2a0b:4e07:e4::/46
At a glance
Subnets
/46 block
Visibility
62 of 62 vantage points
RPKI
Registry
ILAllocated 26th January 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS198186seen on 372 paths from 62 vantage points
- Peer of AS56655seen on 8,762 paths from 127 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
NO
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
- Amsterdam198186566556939213151This path
- London, UK19818656655693951907This path
- Sao Paulo19818656655693932590This path
- Singapore198186566556939132337Shown 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
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
- Israel
- Allocated
- 26th January 2024
- Allocation block
- 2a0b:4e00::/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 |
|---|---|---|
| 2a0b:4e07:e4::/46 | AS198186 | /48 |
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 |
|---|---|---|---|
| 2a0b:4e07:e4::/48 | 65.5k × /64 | AS198186Sondre Hoslemo | 62/62 |
| 2a0b:4e07:e5::/48 | 65.5k × /64 | AS198186Sondre Hoslemo | 62/62 |
| 2a0b:4e07:e6::/48 | 65.5k × /64 | AS198186Sondre Hoslemo | 62/62 |
| 2a0b:4e07:e7::/48 | 65.5k × /64 | AS198186Sondre Hoslemo | 61/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS19818612th 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.