subnet.im

2a12:bec4:17fa::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

24%

15 of 62 vantage points

RPKI

Invalid

Registry

RIPE NCCGB

Allocated 1st April 2022

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2a12:bec4:17fa::/48 as seen from Singapore, read outward from the origin: AS198741 → AS214480 → AS212396 → AS3170 → AS3257 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS198741Amelia KalinowskaOriginAS214480Innova Communicat…AS212396FyfeWeb LtdAS3170VeloxServ Communi…AS3257GTT Communication…AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. Peer of AS198741seen on 15 paths from 15 vantage points
  2. Peer of AS214480seen on 2,386 paths from 141 vantage points
  3. Peer of AS212396seen on 804 paths from 65 vantage points
  4. Peer of AS3170seen on 4,743 paths from 123 vantage points
  5. Peer of AS3257seen on 1,810 paths from 18 vantage points
  6. Peer of AS8966seen on 133,632 paths from 2 vantage points
  7. 7AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore198741214480212396317032578966132337Shown above

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

24%

Seen by 15 of 62 full-feed vantage points

Seen by few vantage points

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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Kingdom
Allocated
1st April 2022
Allocation block
2a12:bec0::/29
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 2a12:bec4:17fa::/48
ROA prefixAuthorised originMax length
2a12:bec4:17f0::/44AS214480/48

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a12:bec4:17fa::/48
PrefixAddressesOriginVisibility
2a12:bec4:17fb::/4865.5k × /64AS214480Innova Communications Limited61/62

History

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