SUBNET.IM

2402:b780:55::/48

Viking Telecom LimitedAS64047

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 5th August 2015

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 4 observed paths to 2402:b780:55::/48, fanning out from AS64047 toward the vantage points that see it. Each path is written out in full beneath the graph.AS64047Viking Telecom Li…OriginAS58779i4HK LimitedAS9304HGC Global Commun…AS132337AxclusiveAS6762Telecom Italia Sp…AS32590Valve CorporationAS6453TATA Communicatio…AS6939Hurricane Electri…AS213151Christian ElsenAS8220COLTAS15576NTS workspace AGAS51907Kanton Zug
  1. Singapore64047587799304132337This path
  2. Sao Paulo64047587799304676232590This path
  3. Amsterdam6404758779930464536939213151This path
  4. London, UK6404758779930482201557651907This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 62 of 62 full-feed vantage points

Globally propagated

Observed at 4 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
Hong Kong SAR China
Allocated
5th August 2015
Allocation block
2402:b780::/32
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 2402:b780:55::/48
ROA prefixAuthorised originMax length
2402:b780::/32AS58779/32
2402:b780::/32AS64047/48

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2402:b780:55::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2402:b780::/32AS640472402:b780:55::/48AS64047This prefix2402:b780:54::/48AS64047

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 2402:b780:55::/48
PrefixAddressesOriginVisibility
2402:b780::/324.3B × /64AS64047Viking Telecom Limited60/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2402:b780:55::/48
PrefixAddressesOriginVisibility
2402:b780:54::/4865.5k × /64AS64047Viking Telecom Limited24/62

History

  1. AS6404712th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Routing data derived from RouteViews MRT archives and public registry data.