subnet.im

195.110.14.0/24

At a glance

Addresses

256

/24 block

Visibility

73%

57 of 78 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 5th January 2007

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 195.110.14.0/24 as seen from Oregon, US, read outward from the origin: AS215607 → AS58212 → AS6453 → AS174 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS215607dataforest GmbHOriginAS58212dataforest GmbHAS6453TATA Communicatio…AS174Cogent Communicat…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS215607seen on 5,120 paths from 140 vantage points
  2. Peer of AS58212seen on 13,770 paths from 69 vantage points
  3. Peer of AS6453seen on 47,167 paths from 41 vantage points
  4. Peer of AS174seen on 158,601 paths from 1 vantage point
  5. Peer of AS8551seen on 1,077,280 paths from 1 vantage 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, UK2156075821264538529This path
  2. Sao Paulo21560758212645335280This path
  3. Amsterdam215607582126453250918298This path
  4. Oregon, US215607582126453174855142013Shown 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

73%

Seen by 57 of 78 full-feed vantage points

Partially propagated

Observed at 4 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
Germany
Allocated
5th January 2007
Allocation block
195.110.14.0/23
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.110.14.0/24
ROA prefixAuthorised originMax length
195.110.14.0/24AS215607/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.110.14.0/24
PrefixAddressesOriginVisibility
195.110.15.0/24256AS12586GHOSTnet GmbH57/78

History

  1. AS21560711th November 2026 — present
  2. AS125868th November 2026 — 11th November 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 195.110.14.0/24 in the calculator/24 reference

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