subnet.im

2.26.184.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 21st September 2010

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2.26.184.0/24 as seen from Singapore, read outward from the origin: AS3257 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS3257GTT Communication…OriginAS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. Peer of AS3257seen on 7,521 paths from 11 vantage points
  2. Peer of AS8966seen on 211,446 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Amsterdam3257250918298This path
  2. London, UK3257129935280This path
  3. Sao Paulo3257645335280This path
  4. Singapore32578966132337Shown above
  5. Oregon, US32572335220130This 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 States
Allocated
21st September 2010
Allocation block
2.26.0.0/15
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 2.26.184.0/24
ROA prefixAuthorised originMax length
2.26.184.0/24AS3257/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 2.26.184.0/24
PrefixAddressesOriginVisibility
2.26.185.0/24256AS401152Ace Data Centers II, L.L.C.78/81

History

  1. AS325722nd September 2026 — present
  2. AS40221512th 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 2.26.184.0/24 in the calculator/24 reference

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