subnet.im

195.178.146.0/24

At a glance

Addresses

256

/24 block

Visibility

94%

75 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 13th December 1996

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 195.178.146.0/24 as seen from Amsterdam, read outward from the origin: AS3319 → AS12687 → AS9002 → AS6453 → AS34549 → AS213151. Each hop is listed with its network name beneath the graph.AS3319User Association …OriginAS12687User Association …AS9002RETN LimitedAS6453TATA Communicatio…AS34549meerfarbig GmbH &…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS3319seen on 2,590 paths from 80 vantage points
  2. Peer of AS12687seen on 3,781 paths from 101 vantage points
  3. Peer of AS9002seen on 212,363 paths from 26 vantage points
  4. Peer of AS6453seen on 82,525 paths from 3 vantage points
  5. Peer of AS34549seen on 716,762 paths from 2 vantage points
  6. 6AS213151Christian 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. London, UK33191268790028529This path
  2. Singapore3319126876939132337This path
  3. Oregon, US331912687693920130This path
  4. Sao Paulo33191268790023356266213This path
  5. Amsterdam3319126879002645334549213151Shown 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

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
Ukraine
Allocated
13th December 1996
Allocation block
195.178.128.0/19
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 195.178.146.0/24
ROA prefixAuthorised originMax length
195.178.146.0/24AS3319/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 195.178.146.0/24
PrefixAddressesOriginVisibility
195.178.147.0/24256AS3319User Association of Ukrainian Research and Academic Network URAN79/80

History

  1. AS20181312th August 2026 present
  2. AS331912th 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 195.178.146.0/24 in the calculator/24 reference

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