122.98.210.0/24
At a glance
Addresses
/24 block
Visibility
77 of 80 vantage points
RPKI
Registry
INAllocated 25th July 2006
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 AS4826seen on 98,695 paths from 94 vantage points
- Peer of AS15412seen on 4,385 paths from 2 vantage points
AU
GB
AEOne 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
- Singapore4826132337This path
- London, UK4826154128529Shown above
- Amsterdam4826154126939213151This path
- Oregon, US482615412693920130This path
- Sao Paulo48261541269393356266213This 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
96%
Seen by 77 of 80 full-feed vantage points
Globally propagatedObserved at 5 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
- APNIC — Asia-Pacific
- Country
- India
- Allocated
- 25th July 2006
- Allocation block
- 122.98.0.0/16
- 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.
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 |
|---|---|---|---|
| 122.98.208.0/22 | 1k | AS4826Vocus Connect International Backbone | 54/80 |
| 122.98.208.0/22 | 1k | AS7474SingTel Optus Pty Ltd | 25/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 122.98.211.0/24 | 256 | AS7474SingTel Optus Pty Ltd | 79/80 |
History
- AS482612th 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.
Open 122.98.210.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.