subnet.im

177.1.198.0/24

Ace Data Centers II, L.L.C.AS401152

Lagom Products LLCAS199180

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

26%

20 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCUS

Allocated 13th March 2025

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: 2 observed paths to 177.1.198.0/24, fanning out from AS199180, AS401152 toward the vantage points that see it. Each path is written out in full beneath the graph.AS401152Ace Data Centers …OriginAS11798Ace Data Centers,…AS6461Zayo BandwidthAS3356Lumen (Level 3)AS23673Cogetel Online, C…AS199180Lagom Products LLCOriginAS50340Selectel - MoscowAS20485JSC TransTeleComAS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Singapore401152117986461335623673This path
  2. Oregon, US19918050340204856762168042013This 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

26%

Seen by 20 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
United States
Allocated
13th March 2025
Allocation block
177.1.192.0/20
Status
allocated
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 177.1.198.0/24
ROA prefixAuthorised originMax length
177.1.198.0/24AS199180/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 177.1.198.0/24
PrefixAddressesOriginVisibility
177.1.199.0/24256AS49505JSC Selectel9/76
177.1.199.0/24256AS401152Ace Data Centers II, L.L.C.66/76

History

  1. AS1991807th November 2026 — present
  2. AS4011527th November 2026 — present
  3. AS19918029th October 2026 — 6th November 2026
  4. AS19918012th August 2026 — 7th 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 177.1.198.0/24 in the calculator/24 reference

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