SUBNET.IM

2a01:8740:ffff:ffe9::/64

Net Info JSCoAS13147

At a glance

Subnets

1 × /64

/64 block

Visibility

2%

1 of 62 vantage points

RPKI

Invalid

Registry

RIPE NCCBG

Allocated 11th 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 2a01:8740:ffff:ffe9::/64, fanning out from AS13147 toward the vantage points that see it. Each path is written out in full beneath the graph.AS13147Net Info JSCoOriginAS57344Telehouse EADAS8966Etisalat (E&)AS132337Axclusive
  1. Singapore13147573448966132337This 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

2%

Seen by 1 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Bulgaria
Allocated
11th July 2012
Allocation block
2a01:8740::/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 2a01:8740:ffff:ffe9::/64
ROA prefixAuthorised originMax length
2a01:8740::/32AS57344/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a01:8740:ffff:ffe9::/64: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a01:8740::/32AS573442a01:8740:ffff:f…AS13147This prefix

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 2a01:8740:ffff:ffe9::/64
PrefixAddressesOriginVisibility
2a01:8740::/324.3B × /64AS57344Telehouse EAD62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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