2a07:54c7:5000::/36
At a glance
Subnets
/36 block
Visibility
61 of 62 vantage points
RPKI
Registry
USAllocated 12th April 2016
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS216455seen on 319 paths from 141 vantage points
- Peer of AS200132seen on 442 paths from 36 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
NL
DEOne 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
- Singapore216455200132132337This path
- Amsterdam2164552001326939213151Shown above
- London, UK216455200132693951907This path
- Sao Paulo2164552001324912713740932590This 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. 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 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
- United States
- Allocated
- 12th April 2016
- Allocation block
- 2a07:54c0::/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 |
|---|---|---|
| 2a07:54c7:5000::/36 | AS216455 | /36 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a07:54c7:5f00::/44 | 1M × /64 | AS215577Lucas van Beek | 62/62 |
| 2a07:54c7:5999::/48 | 65.5k × /64 | AS216455Sting Alleman | 61/62 |
| 2a07:54c7:5f10::/48 | 65.5k × /64 | AS215577Lucas van Beek | 61/62 |
| 2a07:54c7:5ffe::/48 | 65.5k × /64 | AS215577Lucas van Beek | 61/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS21645512th 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.