subnet.im

139.255.220.0/24

At a glance

Addresses

256

/24 block

Visibility

4%

3 of 76 vantage points

RPKI

No ROA

Registry

APNICID

Allocated 30th March 2011

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 139.255.220.0/24 as seen from Sao Paulo, read outward from the origin: AS9905 → AS23700 → AS7717 → AS7713 → AS35280. Each hop is listed with its network name beneath the graph.AS9905PT Link Net TbkOriginAS23700PT Link Net TbkAS7717OpenIXP Route Ser…AS7713PT Telkom Indones…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS9905seen on 82 paths from 3 vantage points
  2. Peer of AS23700seen on 9 paths from 3 vantage points
  3. Peer of AS7717seen on 1,911 paths from 6 vantage points
  4. Peer of AS7713seen on 102,261 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage point

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. Sao Paulo9905237007717771335280Shown 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.

Route visibility

4%

Seen by 3 of 76 full-feed vantage points

Seen by few vantage points

Observed at 3 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
Indonesia
Allocated
30th March 2011
Allocation block
139.255.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.

CoveringMore specific
Prefix hierarchy for 139.255.220.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.139.255.220.0/22AS9905139.255.220.0/24AS9905This prefix

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 139.255.220.0/24
PrefixAddressesOriginVisibility
139.255.220.0/221kAS9905PT Link Net Tbk76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS990525th October 2026 — present
  2. AS990524th September 2026 — 25th October 2026
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 139.255.220.0/24 in the calculator/24 reference

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