subnet.im

31.59.176.0/21

Sachin Kothawade trading as SUN IT SOLUTIONSAS219048

At a glance

Addresses

2,048

/21 block

Visibility

99%

80 of 81 vantage points

RPKI

No ROA

Registry

RIPE NCCAE

Allocated 28th January 2011

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 31.59.176.0/21, fanning out from AS219048 toward the vantage points that see it. Each path is written out in full beneath the graph.AS219048Sachin Kothawade …OriginAS397423Tier.Net Technolo…AS3356Lumen (Level 3)AS35280F5 Networks SARLAS174Cogent Communicat…AS132337AxclusiveAS25091IP-Max SAAS8298IPng Networks GmbHAS6939Hurricane Electri…AS20130Depaul University
  1. London, UK219048397423335635280This path
  2. Sao Paulo219048397423335635280This path
  3. Singapore219048397423174132337This path
  4. Amsterdam2190483974233356250918298This path
  5. Oregon, US2190483974233356693920130This 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 80 of 81 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Arab Emirates
Allocated
28th January 2011
Allocation block
31.56.0.0/14
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 31.59.176.0/21: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.31.59.176.0/21AS219048This prefix31.59.178.0/24AS21906431.59.179.0/24AS21906431.59.180.0/24AS21906431.59.182.0/24AS199742

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 31.59.176.0/21
PrefixAddressesOriginVisibility
31.59.178.0/24256AS219064Akenai Products LTD80/81
31.59.179.0/24256AS219064Akenai Products LTD80/81
31.59.180.0/24256AS219064Akenai Products LTD81/81
31.59.182.0/24256AS199742Akenai Products LTD81/81

Sibling prefixes

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

History

  1. AS21904822nd September 2026 — present
  2. AS4867812th August 2026 — 21st September 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 31.59.176.0/21 in the calculator/21 reference

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