2a03:2887:ff50::/48
At a glance
Subnets
/48 block
Visibility
61 of 63 vantage points
RPKI
Registry
IEAllocated 22nd August 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS63293seen on 137 paths from 137 vantage points
- Peer of AS150125seen on 275 paths from 138 vantage points
- Peer of AS24016seen on 504 paths from 138 vantage points
- Peer of AS45489seen on 218 paths from 48 vantage points
- Peer of AS4635seen on 266 paths from 55 vantage points
- Peer of AS7473seen on 1,210 paths from 46 vantage points
- Peer of AS7474seen on 65 paths from 46 vantage points
- Peer of AS17828seen on 5,449 paths from 121 vantage points
- Peer of AS6939seen on 303,382 paths from 6 vantage points
US
MV
LK
HK
SG
AU
PG
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
- Amsterdam63293150125240164548946357473747417828→ ⋯This path
- London, UK63293150125240164548946357473747417828→ ⋯This path
- Sao Paulo63293150125240164548946357473747417828→ ⋯Shown above
- Singapore63293150125240164548946357473747417828→ ⋯This 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
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
- Ireland
- Allocated
- 22nd August 2011
- Allocation block
- 2a03:2880::/29
- Status
- allocated
- 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 |
|---|---|---|---|
| 2a03:2887:ff51::/48 | 65.5k × /64 | AS63293Meta (CDN Network) | 62/63 |
History
- AS6329312th 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.