subnet.im

193.58.108.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCSC

Allocated 24th October 2018

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 193.58.108.0/24 as seen from Oregon, US, read outward from the origin: AS203273 → AS30823 → AS1299 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS203273NetCrafters OUOriginAS30823aurologic GmbHAS1299Arelion (fka. Tel…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS203273seen on 6,179 paths from 81 vantage points
  2. Peer of AS30823seen on 37,066 paths from 143 vantage points
  3. Peer of AS1299seen on 192,739 paths from 31 vantage points
  4. Peer of AS6939seen on 988,025 paths from 1 vantage point
  5. 5AS20130Depaul UniversityUSVantage 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, UK20327330823129935280This path
  2. Sao Paulo20327330823129935280This path
  3. Singapore203273308231299132337This path
  4. Amsterdam203273308231299250918298This path
  5. Oregon, US203273308231299693920130Shown above

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
Seychelles
Allocated
24th October 2018
Allocation block
193.58.108.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 193.58.108.0/24
ROA prefixAuthorised originMax length
193.58.108.0/24AS203273/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 193.58.108.0/24
PrefixAddressesOriginVisibility
193.58.109.0/24256AS60781LeaseWeb Netherlands B.V.81/81

History

  1. AS20327324th September 2026 — present
  2. AS6078122nd September 2026 — 24th September 2026
  3. AS21911312th 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 193.58.108.0/24 in the calculator/24 reference

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