62.105.198.0/24
At a glance
Addresses
/24 block
Visibility
74 of 76 vantage points
RPKI
Registry
USAllocated 16th October 2002
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 AS401617seen on 212 paths from 138 vantage points
- Peer of AS401541seen on 2,015 paths from 139 vantage points
- Peer of AS38733seen on 7,567 paths from 139 vantage points
- Peer of AS45903seen on 20,130 paths from 139 vantage points
- Peer of AS9304seen on 42,970 paths from 136 vantage points
- Peer of AS6453seen on 653,228 paths from 6 vantage points
VN
HK
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
- London, UK401617401541387334590369398529This path
- Amsterdam4016174015413873345903349182838298This path
- Sao Paulo40161740154138733459039304645335280Shown above
- Singapore40161740154138733459039304463523673This path
- Oregon, US401617401541387334590315412855142013This 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 74 of 76 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United States
- Allocated
- 16th October 2002
- Allocation block
- 62.105.192.0/18
- 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 |
|---|---|---|
| 62.105.198.0/24 | AS401617 | /24 |
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 |
|---|---|---|---|
| 62.105.192.0/18 | 16.4k | AS3257GTT Communications Inc. | 76/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 62.105.199.0/24 | 256 | AS19695Dyfend LLC | 1/76 |
| 62.105.199.0/24 | 256 | AS401560OneCable Network LLC | 75/76 |
History
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 62.105.198.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.