subnet.im

195.211.190.0/24

Net Gate Telecom S.R.L.AS208185

AS43260 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCUA

Allocated 30th October 2009

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: 1 observed path to 195.211.190.0/24, fanning out from AS208185 toward the vantage points that see it. Each path is written out in full beneath the graph.AS208185Net Gate Telecom …OriginAS214941UPCELL TELEKOMUNI…AS68233C1B Telekomunika…AS5405Inter.link GmbHAS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Oregon, US208185214941682354056762168042013This 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.

Route visibility

1%

Seen by 1 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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
30th October 2009
Allocation block
195.211.188.0/22
Status
assigned
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 195.211.190.0/24
ROA prefixAuthorised originMax length
195.211.190.0/24AS0/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.211.190.0/24
PrefixAddressesOriginVisibility
195.211.191.0/24256AS208949HBING LIMITED76/76

History

  1. AS20818529th October 2026 — present
  2. AS4326017th October 2026 — 20th October 2026
  3. AS21142227th September 2026 — 14th October 2026
  4. AS20818512th 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 195.211.190.0/24 in the calculator/24 reference

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