SUBNET.IM

202.59.130.0/24

Route object of Square InformatiX LtdAS38017

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICBD

Allocated 3rd December 2003

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 202.59.130.0/24, fanning out from AS38017 toward the vantage points that see it. Each path is written out in full beneath the graph.AS38017Route object of S…OriginAS58682Level3 Carrier Lt…AS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS20130Depaul University
  1. Singapore3801758682132337This path
  2. Amsterdam38017586826939213151This path
  3. London, UK380175868269398529This path
  4. Sao Paulo38017586826939266213This path
  5. Oregon, US3801758682693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally 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
Bangladesh
Allocated
3rd December 2003
Allocation block
202.59.128.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

Route Origin Authorisations covering 202.59.130.0/24
ROA prefixAuthorised originMax length
202.59.130.0/24AS38017/24
202.59.128.0/20AS38017/22

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 202.59.130.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.202.59.128.0/20AS38017202.59.130.0/24AS38017This prefix202.59.131.0/24AS38017

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 202.59.130.0/24
PrefixAddressesOriginVisibility
202.59.128.0/204.1kAS38017Route object of Square InformatiX Ltd80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 202.59.130.0/24
PrefixAddressesOriginVisibility
202.59.131.0/24256AS38017Route object of Square InformatiX Ltd80/80

History

  1. AS3801712th 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 202.59.130.0/24 in the calculator/24 reference

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