SUBNET.IM

88.80.131.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCBG

Allocated 29th November 2005

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 88.80.131.0/24, fanning out from AS20657 toward the vantage points that see it. Each path is written out in full beneath the graph.AS20657ATLANTIS BG Ltd.OriginAS59900B-IX Route ServersAS213151Christian ElsenAS6762Telecom Italia Sp…AS8529Zain Omantel Inte…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS34224Neterra Ltd.AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. Amsterdam2065759900213151This path
  2. London, UK2065767628529This path
  3. Singapore2065759900132337This path
  4. Oregon, US20657693920130This path
  5. Sao Paulo20657342243356266213This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Bulgaria
Allocated
29th November 2005
Allocation block
88.80.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 88.80.131.0/24
ROA prefixAuthorised originMax length
88.80.131.0/24AS20657/24

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 88.80.131.0/24
PrefixAddressesOriginVisibility
88.80.130.0/24256AS43063SOPHARMA JSCo80/80

History

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

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