2801:c4:37::/48
At a glance
Subnets
/48 block
Visibility
41 of 63 vantage points
RPKI
Registry
MXAllocated 18th August 2023
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS270181seen on 50 paths from 41 vantage points
- Peer of AS8151seen on 206,256 paths from 139 vantage points
- Peer of AS1299seen on 509,875 paths from 6 vantage points
SE
FROne 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
- London, UK2701818151129935280Shown above
- Sao Paulo2701818151291435280This path
- Amsterdam27018181511299250918298This 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
65%
Seen by 41 of 63 full-feed vantage points
Partially propagatedObserved at 3 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
- LACNIC — Latin America and the Caribbean
- Country
- Mexico
- Allocated
- 18th August 2023
- Allocation block
- 2801:c4:37::/48
- Status
- assigned
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 2801:c4:36::/48 | 65.5k × /64 | AS28563Instituto Nacional de Salud Pública | 62/63 |
History
- AS2701817th November 2026 — present
- AS2701816th November 2026 — 6th November 2026
- AS2701815th November 2026 — 5th November 2026
- AS27018126th October 2026 — 4th November 2026
- AS27018126th September 2026 — 25th October 2026
- AS27018124th September 2026 — 25th September 2026
- AS27018112th August 2026 — 23rd September 2026
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.