subnet.im

194.61.239.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCCA

Allocated 24th September 2018

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 194.61.239.0/24, fanning out from AS201667 toward the vantage points that see it. Each path is written out in full beneath the graph.AS201667ASMBP LLCOriginAS137409GSL Networks Pty …AS8298IPng Networks GmbHAS35280F5 Networks SARLAS23673Cogetel Online, C…AS6939Hurricane Electri…AS8529Zain Omantel Inte…AS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam2016671374098298This path
  2. Sao Paulo20166713740935280This path
  3. Singapore20166713740923673This path
  4. London, UK20166713740969398529This path
  5. Oregon, US201667137409855142013This 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
Canada
Allocated
24th September 2018
Allocation block
194.61.236.0/22
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.61.239.0/24
ROA prefixAuthorised originMax length
194.61.239.0/24AS201667/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.61.239.0/24
PrefixAddressesOriginVisibility
194.61.238.0/24256AS219031RoxyCloud Datacenter e Tecnologia LTDA74/76

History

  1. AS2016676th November 2026 — present
  2. AS930429th October 2026 — 6th November 2026
  3. AS1472815th October 2026 — 27th October 2026
  4. AS930412th August 2026 — 6th 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 194.61.239.0/24 in the calculator/24 reference

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