subnet.im

82.23.190.0/24

AS215114 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 28th February 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 82.23.190.0/24 as seen from Sao Paulo, read outward from the origin: AS215035 → AS215114 → AS62000 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS215035CONNECT-IX SASOriginAS215114Stevan Durand--L'…AS62000SERVERD SASAS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Adjacentseen on 609 paths from 141 vantage points
  2. Peer of AS215114seen on 1,698 paths from 138 vantage points
  3. Peer of AS62000seen on 2,151 paths from 49 vantage points
  4. Peer of AS6453seen on 666,978 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. London, UK21503521511419952435280This path
  2. Amsterdam215035215114620001374098298This path
  3. Sao Paulo21503521511462000645335280Shown above
  4. Singapore2150352151146200050263132337This path
  5. Oregon, US215035215114199524693920130This 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 Kingdom
Allocated
28th February 2003
Allocation block
82.22.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 82.23.190.0/24
ROA prefixAuthorised originMax length
82.23.190.0/24AS215035/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

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

History

  1. AS21503512th August 2026 — present
  2. AS21511424th September 2026 — 24th 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 82.23.190.0/24 in the calculator/24 reference

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