subnet.im

2a12:f680:4c8::/45

At a glance

Subnets

524,288 × /64

/45 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCIQ

Allocated 6th December 2021

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:f680:4c8::/45 as seen from Singapore, read outward from the origin: AS51684 → AS57324 → AS212330 → AS208293 → AS211513 → AS211181 → AS57344 → AS132337. Each hop is listed with its network name beneath the graph.AS51684ASIACELL COMMUNIC…OriginAS57324Al Lawn Al Akhdar…AS212330Civilisation Info…AS208293AlSalam State Com…AS211513Al Lawn Al Akhdar…AS211181Civilisation Info…AS57344Telehouse EADAS132337Axclusive

Seen from Singapore

  1. Peer of AS51684seen on 3,681 paths from 142 vantage points
  2. Peer of AS57324seen on 5,356 paths from 142 vantage points
  3. Peer of AS212330seen on 28,759 paths from 142 vantage points
  4. Peer of AS208293seen on 15,230 paths from 142 vantage points
  5. Peer of AS211513seen on 3,858 paths from 142 vantage points
  6. Peer of AS211181seen on 11,763 paths from 142 vantage points
  7. Peer of AS57344seen on 1,383 paths from 2 vantage points
  8. 8AS132337AxclusiveSGVantage 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. Sao Paulo51684210513208293210021693932590This path
  2. London, UK516842105132082932100211743428851907This path
  3. Amsterdam516845732421233020829321151321118157344213151This path
  4. Singapore516845732421233020829321151321118157344132337Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

98%

Seen by 61 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Iraq
Allocated
6th December 2021
Allocation block
2a12:f680::/29
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 2a12:f680:4c8::/45
ROA prefixAuthorised originMax length
2a12:f680:4c8::/45AS51684/45

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:f680:4c8::/45
PrefixAddressesOriginVisibility
2a12:f680:4c0::/45524k × /64AS51684ASIACELL COMMUNICATIONS PJSC61/62

History

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