subnet.im

193.178.115.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCES

Allocated 18th November 2019

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 193.178.115.0/24 as seen from Singapore, read outward from the origin: AS30088 → AS63023 → AS3257 → AS3356 → AS23673. Each hop is listed with its network name beneath the graph.AS30088GTHostOriginAS63023GTHostAS3257GTT Communication…AS3356Lumen (Level 3)AS23673Cogetel Online, C…

Seen from Singapore

  1. 1AS30088GTHostUSOrigin
    Peer of AS30088seen on 2,607 paths from 76 vantage points
  2. Peer of AS63023seen on 48,638 paths from 119 vantage points
  3. Peer of AS3257seen on 224,634 paths from 53 vantage points
  4. Peer of AS3356seen on 421,631 paths from 2 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. Amsterdam30088630233257250918298This path
  2. London, UK3008863023325712998529This path
  3. Sao Paulo3008863023174645335280This path
  4. Singapore30088630233257335623673Shown above
  5. Oregon, US3008863023174855142013This 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

99%

Seen by 75 of 76 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
Spain
Allocated
18th November 2019
Allocation block
193.178.115.0/24
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.178.115.0/24
ROA prefixAuthorised originMax length
193.178.115.0/24AS30088/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.178.115.0/24
PrefixAddressesOriginVisibility
193.178.114.0/24256AS207375Fiber Operator B.V.76/76

History

  1. AS3008816th October 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.178.115.0/24 in the calculator/24 reference

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