124.66.209.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
KRAllocated 14th January 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS216138seen on 1,470 paths from 81 vantage points
- Peer of AS398704seen on 1,377 paths from 80 vantage points
- Peer of AS138195seen on 7,607 paths from 81 vantage points
- Peer of AS138415seen on 5,483 paths from 95 vantage points
- Peer of AS17476seen on 5,808 paths from 86 vantage points
- Peer of AS6453seen on 102,232 paths from 5 vantage points
- Peer of AS25091seen on 666,966 paths from 2 vantage points
GB
US
HK
CHOne 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
- Singapore21613839870413819513841517476132337This path
- London, UK21613839870413819513841517476291435280This path
- Sao Paulo21613839870413819513841517476645335280This path
- Oregon, US21613839870413819513841517476693920130This path
- Amsterdam216138398704138195138415174766453250918298Shown 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 81 of 81 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
- 14th January 2011
- Allocation block
- 124.66.208.0/20
- 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 |
|---|---|---|
| 124.66.209.0/24 | AS216138 | /24 |
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 |
|---|---|---|---|
| 124.66.208.0/24 | 256 | AS138195MOACK.Co.LTD | 81/81 |
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 124.66.209.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.