subnet.im

176.97.217.0/24

At a glance

Addresses

256

/24 block

Visibility

54%

41 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCGE

Allocated 25th October 2021

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 176.97.217.0/24 as seen from Singapore, read outward from the origin: AS199242 → AS19257 → AS2914 → AS23673. Each hop is listed with its network name beneath the graph.AS199242Malakmadze Web LLCOriginAS19257SUBRIGO CORPORATI…AS2914NTT America, Inc.AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS199242seen on 747 paths from 76 vantage points
  2. Peer of AS19257seen on 2,734 paths from 105 vantage points
  3. Peer of AS2914seen on 78,227 paths from 1 vantage 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. Amsterdam2192785944769398298This path
  2. London, UK2192785944769398529This path
  3. Sao Paulo21927859447693935280This path
  4. Singapore19924219257291423673Shown above
  5. Oregon, US2192785944769391299855142013This 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

54%

Seen by 41 of 76 full-feed vantage points

Partially propagated

Observed at 4 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
Georgia
Allocated
25th October 2021
Allocation block
176.97.217.0/24
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 176.97.217.0/24
ROA prefixAuthorised originMax length
176.97.217.0/24AS199242/24
176.97.217.0/24AS219278/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 176.97.217.0/24
PrefixAddressesOriginVisibility
176.97.216.0/24256AS29684Nour Internet Company for Communications and Information Technology Ltd.76/76

History

  1. AS1992425th November 2026 — present
  2. AS2192787th November 2026 — present
  3. AS21927829th October 2026 — 5th November 2026
  4. AS19924212th August 2026 — 31st 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 176.97.217.0/24 in the calculator/24 reference

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