subnet.im

2.58.86.0/24

At a glance

Addresses

256

/24 block

Visibility

94%

75 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCLT

Allocated 21st March 2019

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2.58.86.0/24 as seen from London, UK, read outward from the origin: AS42831 → AS137409 → AS8529. Each hop is listed with its network name beneath the graph.AS42831UK Dedicated Serv…OriginAS137409GSL Networks Pty …AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS42831seen on 319 paths from 1 vantage point
  2. Peer of AS137409seen on 91,764 paths from 6 vantage points

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. Singapore42831132337This path
  2. London, UK428311374098529Shown above
  3. Oregon, US42831693920130This path
  4. Amsterdam42831325734549213151This path
  5. Sao Paulo4283129143356266213This 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

94%

Seen by 75 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
Lithuania
Allocated
21st March 2019
Allocation block
2.58.84.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 2.58.86.0/24
ROA prefixAuthorised originMax length
2.58.86.0/24AS42831/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.58.86.0/24
PrefixAddressesOriginVisibility
2.58.87.0/24256AS61596Huge Networks Segurança da Informação LTDA80/80

History

  1. AS4283112th August 2026 present
  2. AS14211112th 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 2.58.86.0/24 in the calculator/24 reference

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