subnet.im

195.58.129.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCDK

Allocated 6th November 1996

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 195.58.129.0/24 as seen from Singapore, read outward from the origin: AS31715 → AS10122 → AS23764 → AS23673. Each hop is listed with its network name beneath the graph.AS31715CloudIP LLCOriginAS10122NETSTAR (SG) PTE.…AS23764China Telecom Glo…AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS31715seen on 2,718 paths from 76 vantage points
  2. Peer of AS10122seen on 270 paths from 1 vantage point
  3. Peer of AS23764seen on 30,201 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. Amsterdam31715101228298This path
  2. London, UK31715101228529This path
  3. Sao Paulo3171510122423035280This path
  4. Singapore31715101222376423673Shown above
  5. Oregon, US3171510122855142013This 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 76 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
Denmark
Allocated
6th November 1996
Allocation block
195.58.128.0/21
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.58.129.0/24
ROA prefixAuthorised originMax length
195.58.129.0/24AS31715/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.58.129.0/24
PrefixAddressesOriginVisibility
195.58.128.0/24256AS198566MAMUT RAHAL SOFTWARE - FZCO76/76

History

  1. AS3171528th October 2026 — present
  2. AS15441012th August 2026 — 14th October 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.58.129.0/24 in the calculator/24 reference

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