2a01:ffc7:ff::/48
At a glance
Subnets
/48 block
Visibility
62 of 62 vantage points
RPKI
Registry
NOAllocated 30th October 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS215295seen on 62 paths from 62 vantage points
- Peer of AS210152seen on 838 paths from 142 vantage points
- Peer of AS206260seen on 2,208 paths from 142 vantage points
- Peer of AS34087seen on 434 paths from 15 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
US
SGOne 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
- Amsterdam215295210152206260340876939213151This path
- Sao Paulo21529521015220626034087335632590This path
- Singapore215295210152206260340876939132337Shown above
- London, UK215295210152206260340871299900251907This 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
100%
Seen by 62 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
- Norway
- Allocated
- 30th October 2024
- Allocation block
- 2a01:ffc0::/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 |
|---|---|---|
| 2a01:ffc7::/40 | AS215295 | /48 |
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 |
|---|---|---|---|
| 2a01:ffc7:fe::/48 | 65.5k × /64 | AS215295Skyfritt AS | 61/62 |
History
- AS21529512th 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.