2610:b0:41d8::/47
At a glance
Subnets
/47 block
Visibility
63 of 65 vantage points
RPKI
Registry
USAllocated 28th July 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS3573seen on 129 paths from 63 vantage points
- Peer of AS2685seen on 2,909 paths from 131 vantage points
- Peer of AS7018seen on 116,430 paths from 52 vantage points
- Peer of AS1299seen on 341,215 paths from 5 vantage points
- Peer of AS25091seen on 666,145 paths from 2 vantage points
SE
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
- Singapore357326856939132337This path
- London, UK357326857018129935280This path
- Sao Paulo357326857018645335280This path
- Amsterdam3573268570181299250918298Shown 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 63 of 65 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
- ARIN — North America
- Country
- United States
- Allocated
- 28th July 2006
- Allocation block
- 2610:b0::/32
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2610:b0::/33 | 2.1B × /64 | AS3573Accenture LLP | 64/65 |
| 2610:b0::/32 | 4.3B × /64 | AS3573Accenture LLP | 65/65 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2610:b0:41d8::/48 | 65.5k × /64 | AS3573Accenture LLP | 63/65 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS357312th 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.