SUBNET.IM

200.59.228.0/22

Neunet S.A.AS27751

At a glance

Addresses

1,024

/22 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICAR

Allocated 17th November 2004

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 200.59.228.0/22, fanning out from AS27751 toward the vantage points that see it. Each path is written out in full beneath the graph.AS27751Neunet S.A.OriginAS7049Silica Networks A…AS213151Christian ElsenAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam277517049213151This path
  2. London, UK2775133568529This path
  3. Sao Paulo277517049266213This path
  4. Singapore277517049132337This path
  5. Oregon, US277513356693920130This 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

99%

Seen by 79 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
LACNIC — Latin America and the Caribbean
Country
Argentina
Allocated
17th November 2004
Allocation block
200.59.224.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 200.59.228.0/22
ROA prefixAuthorised originMax length
200.59.224.0/20AS27751/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 200.59.228.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.200.59.228.0/22AS27751This prefix200.59.228.0/23AS27751200.59.230.0/23AS27751200.59.228.0/24AS27751200.59.229.0/24AS27751200.59.230.0/24AS27751+1 more

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 200.59.228.0/22
PrefixAddressesOriginVisibility
200.59.228.0/23512AS27751Neunet S.A.80/80
200.59.230.0/23512AS27751Neunet S.A.80/80
200.59.228.0/24256AS27751Neunet S.A.12/80
200.59.229.0/24256AS27751Neunet S.A.12/80
200.59.230.0/24256AS27751Neunet S.A.12/80
200.59.231.0/24256AS27751Neunet S.A.12/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 200.59.228.0/22
PrefixAddressesOriginVisibility
200.59.224.0/221kAS27751Neunet S.A.79/80

History

  1. AS2775112th 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 200.59.228.0/22 in the calculator/22 reference

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