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

AS138182 — CNGI-SJZ-IX-AS-AP - CERNET2 regional IX at Hebei Normal University

🇨🇳 China · APNIC region · approx. 40.00, 116.32

CNGI-SJZ-IX-AS-AP - CERNET2 regional IX at Hebei Normal University (AS138182) in China has 1 direct BGP neighbours, ranked #67069 of 88104 by observed links.

#67069 rank by links (of 88104)
1 direct neighbours
0 IPv4 prefixes
124 IPv6 prefixes
0 upstream providers
1 peers
0 downstream customers
0 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/138182/summary.json.

Embed this badge

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

BGPVerse badge for AS138182 — CNGI-SJZ-IX-AS-AP - CERNET2 regional IX at Hebei Normal University

Network intelligence

0 MOAS prefixes
124 more-specific prefixes
5.0 avg. AS path length (5–5)

Neighbourhood

What's directly and indirectly (up to two hops) connected to AS138182 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS138182 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 →

AS138182 — CNGI-SJZ-IX-AS-AP - CERNET2 regional IX at Hebei Normal University AS138182 AS23910 — CNGI-CERNET2-AS-AP - China Next Generation Internet CERNET2 AS23910 AS4134 — CHINANET-BACKBONE - No.31,Jin-rong Street AS4134 AS4538 — ERX-CERNET-BKB - China Education and Research Network Center AS4538 AS23911 — CNGI-BJIX-AS-AP - China Next Generation Internet Beijing IX AS23911 AS133111 — CNT-northChina - CERNET New Technology Co., Ltd AS133111 AS24348 — CNGI-BJ-IX2-AS-AP - CERNET2 IX at Tsinghua University AS24348 AS24369 — CNGI-SY-IX-AS-AP - CERNET2 IX at Northeast University AS24369 AS24361 — CNGI-NJ-IX-AS-AP - CERNET2 IX at Southeast University AS24361 AS133512 — CERNEWTECH-ZHENGZHOU - CERNET New Technology Co., Ltd AS133512 AS24364 — CNGI-SH-IX-AS-AP - CERNET2 IX at Shanghai Jiaotong University AS24364 AS24357 — CNGI-GZ-IX-AS-AP - CERNET2 IX at South China University of Technology AS24357 AS24349 — CNGI-BJ-IX3-AS-AP - CERNET2 IX at Peking University AS24349 AS24368 — CNGI-XMN-IX-AS-AP - CERNET2 IX at Xiamen University AS24368 AS24371 — CNGI-CHC-IX-AS-AP - CERNET2 IX at Jilin University AS24371 AS24358 — CNGI-WH-IX-AS-AP - CERNET2 IX at Huazhong University of Science and Technology AS24358 AS24353 — CNGI-XA-IX-AS-AP - CERNET2 IX at Xi'an Jiaotong University AS24353 AS24352 — CNGI-TJN-IX-AS-AP - CERNET2 IX at Tianjin University AS24352 AS24367 — CNGI-HZH-IX-AS-AP - CERNET2 IX at Zhejiang University AS24367 AS138369 — CNGI-SZH-IX-AS-AP - CERNET2 regional IX at Shenzhen University AS138369 AS24363 — CNGI-JNN-IX-AS-AP - CERNET2 IX at Shandong University AS24363 AS24360 — CNGI-ZHZ-IX-AS-AP - CERNET2 IX at Zhengzhou University AS24360 AS24365 — CNGI-SH-IX2-AS-AP - CERNET2 IX at Fudan University AS24365 AS24366 — CNGI-SH-IX3-AS-AP - CERNET2 IX at Tongji University AS24366 AS24359 — CNGI-CHS-IX-AS-AP - CERNET2 IX at Central South University AS24359 AS24356 — CNGI-CHQ-IX-AS-AP - CERNET2 IX at Chongqing University AS24356 AS24355 — CNGI-CD-IX-AS-AP - CERNET2 IX at University of Electronic Science and Technology of China AS24355

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 104 more.

Peers (1)

Networks this AS exchanges traffic with directly, as equals (neither is the other's transit customer).

Geographic footprint

Geolocated (estimated) country of every prefix AS138182 announces, via IP geolocation against DB-IP City Lite — not AS138182'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