subnet.im

194.58.223.0/24

HOSTKEY B.V.AS57043

At a glance

Addresses

256

/24 block

Visibility

98%

79 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCCZ

Allocated 13th June 1994

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 194.58.223.0/24 as seen from Amsterdam, read outward from the origin: AS57043 → AS9002 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS57043HOSTKEY B.V.OriginAS9002RETN LimitedAS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. 1AS57043HOSTKEY B.V.NLOrigin
    Peer of AS57043seen on 12,599 paths from 125 vantage points
  2. 2AS9002RETN LimitedGB
    Peer of AS9002seen on 28,941 paths from 5 vantage points
  3. 3AS25091IP-Max SACH
    Peer of AS25091seen on 666,966 paths from 2 vantage points
  4. 4AS8298IPng Networks GmbHCHVantage 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. Singapore57043174132337This path
  2. Oregon, US57043693920130This path
  3. Amsterdam570439002250918298Shown above
  4. London, UK57043174129935280This path
  5. Sao Paulo57043174335635280This 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

98%

Seen by 79 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
Czechia
Allocated
13th June 1994
Allocation block
194.58.222.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 194.58.223.0/24
ROA prefixAuthorised originMax length
194.58.223.0/24AS57043/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 194.58.223.0/24
PrefixAddressesOriginVisibility
194.58.222.0/24256AS198180Gabriele Sabatino81/81

History

  1. AS5704324th September 2026 — present
  2. AS21942912th 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 194.58.223.0/24 in the calculator/24 reference

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