BGPVerse by Vautron View on the live map v0.1.57 (0ea09d57)

AS208555 — Mobinhost Dade Pardazi Mobinhost Co LTD

🇮🇷 Iran · RIPE NCC region · approx. 35.73, 51.38

Mobinhost Dade Pardazi Mobinhost Co LTD (AS208555) in Iran has 6 direct BGP neighbours, ranked #14315 of 88104 by observed links.

#14315 rank by links (of 88104)
6 direct neighbours
22 IPv4 prefixes
0 IPv6 prefixes
3 upstream providers
0 peers
3 downstream customers
3 customer cone size

Copy network summary

A short plain-text summary of this AS, ready to paste into a chat, forum post or ticket.

Prefer JSON? The same facts are at /as/208555/summary.json.

Embed this badge

Show this AS's current stats on your own website, linking back here.

BGPVerse badge for AS208555 — Mobinhost Dade Pardazi Mobinhost Co LTD

Network intelligence

0 MOAS prefixes
22 more-specific prefixes
4.4 avg. AS path length (4–7)

Neighbourhood

What's directly and indirectly (up to two hops) connected to AS208555 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS208555 itself always centred. Drag to pan, scroll/pinch to zoom, click a dot to jump to that AS's own page. Explore the full interactive map →

AS208555 — Mobinhost Dade Pardazi Mobinhost Co LTD AS208555 AS42337 — RESPINA-AS Respina Networks & Beyond PJSC AS42337 AS25184 — AFRANET Afranet AS25184 AS60976 — POL Parsan Lin Co. PJS AS60976 AS198596 — Mojtaba-Imani Seyed Mojtaba Imani AS198596 AS51026 — MobinhostInfrastructure Dade Pardazi Mobinhost Co LTD AS51026 AS215708 — mobinidc Mobin Arvand Infrastructure Company LTD AS215708 AS34927 — iFog-GmbH iFog GmbH AS34927 AS49666 — TIC-GW-AS Telecommunication Infrastructure Company AS49666 AS43754 — ASIATECH Asiatech Data Transmission company AS43754 AS48011 — DigiTurunc Turunc Smart Bilgisayar Teknoloji Ve Dis Ticaret Limited Sirketi AS48011 AS49100 — IR-THR-PTE Pishgaman Toseeh Ertebatat Company (Private Joint Stock) AS49100 AS24631 — FANAPTELECOM-FCP Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS AS24631 AS41881 — Fanava-AS Fanava Group AS41881 AS12880 — DCI-AS Iran Information Technology Company PJSC AS12880 AS44889 — AZMA-AS Farhang Azma Communications Company LTD AS44889 AS206065 — FDI Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS AS206065 AS44400 — IR-FCP Ertebatat Sabet Parsian Co. PJS AS44400 AS48147 — AminIDC Asre Pardazeshe Ettelaate Amin Institute AS48147 AS204104 — GSC Giti Secure Cloud LLC AS204104 AS34837 — IRANET-IPM Institute for Research in Fundamental Sciences AS34837 AS205207 — AbreNik-Cloud Padiz Dadeh Resan PJSC AS205207 AS47376 — WGB-LLC Web Gostaran Bandar Company (PJS) AS47376 AS49972 — FANHAB NAMAVARAN e ASR e Novin Information Technology (FANHAB) , Private Joint-Stock Co AS49972 AS197946 — AnyCast Amnpardaz Soft Corporation AS197946 AS204203 — Sepehr-Sabz-DC-TEH Atrin Information & Communications Technology Company PJS AS204203 AS204650 — ErtebatateSabeteAvaArvand Toloe Rayaneh Loghman Educational and Cultural Co. LTD AS204650 AS202468 — AbrArvan-AS Noyan Abr Arvan Co. ( Private Joint Stock) AS202468 AS61173 — GWSN-AS Green Web Samaneh Novin PJSC AS61173 AS214171 — Foojan Foojan Cloud Computing Co. PJS AS214171 AS59441 — Hostiran-Network NOAVARAN SHABAKEH SABZ MEHREGAN (Ltd.) AS59441 AS204213 — netmihan Netmihan Communication Company Ltd AS204213

Announced prefixes

RPKI route-origin validity badge per prefix, from this instance's self-hosted Routinator (see Credits). The full, de-duplicated set seen across every BGP collector this snapshot imports — usually more than the “IPv4/IPv6 prefixes” counts above, which only reflect a single collector's own routing table.

...and 2 more.

Upstream providers (3)

Networks that this AS is a customer of (inferred from public BGP data by BGPKIT's as2rel dataset, a heuristic, not ground truth).

Downstream customers (3)

Networks that are, in turn, this AS's own customers.

Geographic footprint

Geolocated (estimated) country of every prefix AS208555 announces, via IP geolocation against DB-IP City Lite — not AS208555's RIR registration country (see the stats above), and not necessarily where its infrastructure physically sits.

What am I looking at?

Autonomous Systems (AS)

An Autonomous System (AS) is a network, or group of networks, run by one organisation — an internet provider, a university, a cloud provider, a company's own network — that has its own block of IP addresses and decides, as a single unit, how traffic enters and leaves it. This page describes exactly one AS; the full interactive map shows all of them at once, as a graph.

What connects ASes: BGP

The "Upstream providers" / "Peers" / "Downstream customers" sections above, and the connections on the full map, are not physical cables; they are observed routing relationships via BGP (Border Gateway Protocol), the protocol that networks use to tell each other which IP address ranges they can reach. See BGP on Wikipedia for the full protocol details.

Upstream / peer / downstream customer

These relationship labels are an inference, not something BGP itself announces directly: BGPKIT's free as2rel dataset infers them from patterns in public BGP data (e.g. whether a path through two networks looks like paid transit or settlement-free peering). Treat it as a useful heuristic, not ground truth. Customer cone size (shown above, where this data covers enough of this AS's own links) counts every AS transitively reachable via downstream customer links only — roughly, how many networks ultimately rely on this AS to reach the rest of the Internet.

MOAS prefixes and more-specific prefixes

MOAS (Multiple Origin AS) means a prefix is announced by more than one AS at the same time — usually anycast or multihoming via two upstreams, occasionally a route leak or hijack; this count alone cannot tell those apart. A more-specific prefix is a smaller sub-block of a broader prefix this AS (or another AS) also announces, e.g. a /25 alongside a /24 covering it — common and usually deliberate traffic engineering, not inherently a problem.

RPKI: is this prefix authorised to be announced?

RPKI (Resource Public Key Infrastructure) lets the holder of a prefix publish a signed ROA (Route Origin Authorization) stating exactly which AS may originate it. Valid: a matching ROA exists. Invalid: a ROA exists but for a different AS or a shorter maximum length. Not Found: no ROA covers this prefix at all — still the normal case for most of the Internet today.

Countries and RIRs

Every AS is registered in one country (RIPE NCC AS names list) and, by extension, in the world region served by one of the five Regional Internet Registries (RIRs) — AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC — the nonprofit bodies that allocate IP address space and AS numbers within their region. Browse by country or by RIR to see every AS registered there.

Full explainer, glossary and data provenance: see the main map's own Help button, or the Credits dialog linked in the footer above.

Privacy & cookies

BGPVerse sets no cookies and uses no analytics, advertising or third-party trackers of any kind.

This page itself stores nothing in your browser (it has no settings of its own to remember). The main interactive map does store your own display preferences (pulse duration, colour mode, etc.) in localStorage — see its own Privacy dialog, reachable from the footer there, to clear that.

Server-side, your IP address is used only transiently (in memory, never written to disk beyond a request-path access log line without the query itself) for rate limiting; see the Credits & data sources dialog for where the map data itself comes from.

Credits & data sources

Operated by

BGPVerse is built and run by Vautron Rechenzentrum AG, a data centre and managed-hosting provider based in Regensburg, Germany — this map is one of our side projects, not a product.

Looking for servers, cloud or network services of your own? Visit vautron.de →

BGP data

“The RIPE Routing Information Service (RIS) is a RIPE NCC service. With the help of network operators all over the world, RIS employs a globally distributed set of Remote Route Collectors (RRCs), typically located at Internet Exchange Points, to collect and store Internet routing data.”

RIPE RIS's own route collectors sit mostly at European/major Internet exchange points; RouteViews (University of Oregon) route collector data fills in several collectors RIS itself has few or none near — Nairobi (KIXP), Johannesburg (NAPAfrica), São Paulo (IX.br), Bangkok (BKNIX) and Hong Kong (HKIX) — for a somewhat broader view of the Internet's edges. Data are archived and made publicly available for download at archive.routeviews.org. Used under its CC BY 4.0 licence.

AS names and registration countries (shown above as each AS's own country, independent of any IP geolocation): RIPE NCC AS names list. RIR (Regional Internet Registry) region assignment is derived from that same registration country via the NRO's own public country-to-RIR table, not a per-resource delegation record, so it is an approximation for the rare legacy/historically-reassigned resource. Approximate AS locations: IP Geolocation by DB-IP (DB-IP City Lite, refreshed daily, derived from a sample of each AS's announced prefixes — not the AS's actual location, and not the same thing as its registration country); the same database also resolves the “Geographic footprint” section above (where appropriate) — a geolocated, estimated country per prefix, again not the registration country — this time against every announced prefix rather than a sample. AS relationships (upstream provider / peer / downstream customer, shown above) are an inference, not ground truth, from BGPKIT's free as2rel dataset, refreshed daily. Icons: a small selection from Font Awesome Free (CC BY 4.0), self-hosted, not loaded from a CDN.

RPKI validation

RPKI route-origin validity badges (prefix list above), when enabled by the operator, are computed by a self-hosted Routinator instance (NLnet Labs, BSD-3-Clause), which fetches and validates Route Origin Authorizations (ROAs) directly from the public RPKI repositories of the five Regional Internet Registries. See the Help dialog for what the badges mean.

Software

Data pipeline status

Whether BGPVerse's own background data pipeline is currently up to date — not just whether the server itself is reachable. Also available as its own page/JSON endpoint: /status.

…

View full AS page