subnet.im

69.90.128.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 6th November 2003

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 69.90.128.0/24 as seen from Sao Paulo, read outward from the origin: AS218661 → AS62610 → AS21859 → AS1299 → AS35280. Each hop is listed with its network name beneath the graph.AS218661ACO TECH SERVICES…OriginAS62610Zenlayer IncAS21859Zenlayer IncAS1299Arelion (fka. Tel…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS218661seen on 1,108 paths from 81 vantage points
  2. Peer of AS62610seen on 59,346 paths from 145 vantage points
  3. Peer of AS21859seen on 25,104 paths from 139 vantage points
  4. Peer of AS1299seen on 513,543 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage 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. Amsterdam21866162610218598298This path
  2. London, UK218661626102185935280This path
  3. Singapore2186616261021859132337This path
  4. Sao Paulo2186616261021859129935280Shown above
  5. Oregon, US2186616261021859693920130This 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 81 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
6th November 2003
Allocation block
69.90.128.0/22
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 69.90.128.0/24
ROA prefixAuthorised originMax length
69.90.128.0/24AS218661/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 69.90.128.0/24
PrefixAddressesOriginVisibility
69.90.129.0/24256AS218661ACO TECH SERVICES LTD80/81

History

  1. AS21866125th September 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 69.90.128.0/24 in the calculator/24 reference

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