SUBNET.IM

211.253.61.0/24

At a glance

Addresses

256

/24 block

Visibility

53%

42 of 80 vantage points

RPKI

No ROA

Registry

APNICKR

Allocated 8th September 2000

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 211.253.61.0/24 as seen from Sao Paulo, read outward from the origin: AS17574 → AS9318 → AS701 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS17574Seoul Metropolita…OriginAS9318SK Broadband Co L…AS701Verizon BusinessAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS17574seen on 468 paths from 48 vantage points
  2. Peer of AS9318seen on 4,858 paths from 51 vantage points
  3. Peer of AS701seen on 154,209 paths from 64 vantage points
  4. Peer of AS3356seen on 997,311 paths from 2 vantage points

One 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

  1. Singapore175749318132337This path
  2. Amsterdam1784147666939213151This path
  3. London, UK17574931841348529This path
  4. Sao Paulo1757493187013356266213Shown above
  5. Oregon, US175749318129932572335220130This 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

53%

Seen by 42 of 80 full-feed vantage points

Partially propagated

Observed 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
8th September 2000
Allocation block
211.252.0.0/15
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.

CoveringMore specific
Prefix hierarchy for 211.253.61.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.211.252.0.0/15AS4766211.253.60.0/24AS17574211.253.61.0/24AS17574This prefix211.253.60.0/24AS17841

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

Announcements that contain 211.253.61.0/24
PrefixAddressesOriginVisibility
211.252.0.0/15131kAS4766Korea Telecom80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 211.253.61.0/24
PrefixAddressesOriginVisibility
211.253.60.0/24256AS17574Seoul Metropolitan Government Computer Center24/80
211.253.60.0/24256AS17841NATIONAL INFORMATION RESOURCES SERVICE56/80

History

  1. AS1757412th August 2026 present
  2. AS1784112th 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 211.253.61.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.