SUBNET.IM

193.24.125.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRS

Allocated 3rd July 2024

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 193.24.125.0/24 as seen from Amsterdam, read outward from the origin: AS48708 → AS44306 → AS5511 → AS34549 → AS213151. Each hop is listed with its network name beneath the graph.AS48708Omax Network d.o.…OriginAS44306OMONIA d.o.o.AS5511Orange S.A.AS34549meerfarbig GmbH &…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS48708seen on 182 paths from 78 vantage points
  2. Peer of AS44306seen on 1,016 paths from 76 vantage points
  3. Peer of AS5511seen on 40,711 paths from 3 vantage points
  4. Peer of AS34549seen on 716,762 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage 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. Singapore487084256021215132337This path
  2. Amsterdam4870844306551134549213151Shown above
  3. London, UK4870844306551112998529This path
  4. Sao Paulo487084430655113356266213This path
  5. Oregon, US48708443065511693920130This 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 80 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
Serbia
Allocated
3rd July 2024
Allocation block
193.24.125.0/24
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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.24.125.0/24
PrefixAddressesOriginVisibility
193.24.124.0/24256AS215057Opera della Primaziale Pisana79/80

History

  1. AS4870812th 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 193.24.125.0/24 in the calculator/24 reference

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