2a12:f680:4f0::/45
At a glance
Subnets
/45 block
Visibility
61 of 63 vantage points
RPKI
Registry
IQAllocated 6th December 2021
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS51684seen on 3,940 paths from 138 vantage points
- 2AS57324Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.IQPeer of AS57324seen on 5,344 paths from 139 vantage points
- Peer of AS212330seen on 28,933 paths from 139 vantage points
- Peer of AS208293seen on 15,411 paths from 139 vantage points
- 5AS211513Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.IQPeer of AS211513seen on 3,822 paths from 138 vantage points
- Peer of AS211181seen on 11,890 paths from 138 vantage points
- Peer of AS57344seen on 1,168 paths from 2 vantage points
BG
CHOne 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
- Singapore51684210513208293210021132337This path
- London, UK51684210513208293210021129935280This path
- Sao Paulo516842105132082932100211299291435280This path
- Amsterdam5168457324212330208293211513211181573448298Shown 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
97%
Seen by 61 of 63 full-feed vantage points
Globally propagatedObserved 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
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2a12:f680:4f0::/45 | AS51684 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a12:f680:4f8::/45 | 524k × /64 | AS51684ASIACELL COMMUNICATIONS PJSC | 61/63 |
History
- 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.