210.211.83.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
KRAllocated 24th September 2009
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 AS17607seen on 640 paths from 80 vantage points
- Peer of AS9318seen on 46,996 paths from 64 vantage points
- Peer of AS2914seen on 230,275 paths from 62 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
US
BROne 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
- Singapore176079318132337This path
- Amsterdam1760793186939213151This path
- London, UK17607931841348529This path
- Oregon, US176079318693920130This path
- Sao Paulo17607931829143356266213Shown 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 80 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
- South Korea
- Allocated
- 24th September 2009
- Allocation block
- 210.211.64.0/19
- 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 |
|---|---|---|---|
| 210.211.64.0/19 | 8.2k | AS10049SK Co., | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 210.211.82.0/24 | 256 | AS17607Mirae Asset Life Insurance Co., Ltd | 80/80 |
History
- AS1760712th 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 210.211.83.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.