SUBNET.IM

2404:8300:2::/48

Special Communication OrganizationAS18053

At a glance

Subnets

65,536 × /64

/48 block

Visibility

11%

7 of 62 vantage points

RPKI

Invalid

Registry

APNICPK

Allocated 20th July 2012

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: 1 observed path to 2404:8300:2::/48, fanning out from AS18053 toward the vantage points that see it. Each path is written out in full beneath the graph.AS18053Special Communica…OriginAS38193Transworld Associ…AS8966Etisalat (E&)AS132337Axclusive
  1. Singapore18053381938966132337This 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.

Route visibility

11%

Seen by 7 of 62 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Pakistan
Allocated
20th July 2012
Allocation block
2404:8300::/32
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2404:8300:2::/48
ROA prefixAuthorised originMax length
2404:8300::/32AS18053/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2404:8300:2::/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.2404:8300::/32AS180532404:8300:2::/48AS18053This prefix2404:8300:3::/48AS18053

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 2404:8300:2::/48
PrefixAddressesOriginVisibility
2404:8300::/324.3B × /64AS18053Special Communication Organization62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2404:8300:2::/48
PrefixAddressesOriginVisibility
2404:8300:3::/4865.5k × /64AS18053Special Communication Organization7/62

History

  1. AS1805312th 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.