subnet.im

176.97.205.0/24

At a glance

Addresses

256

/24 block

Visibility

14%

11 of 80 vantage points

RPKI

Invalid

Registry

RIPE NCCUA

Allocated 22nd 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.205.0/24 as seen from Singapore, read outward from the origin: AS63902 → AS18186 → AS7473 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS63902SHINE TELECOM CO.…OriginAS18186Nebula Global LLCAS7473Singapore Telecom…AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. Peer of AS63902seen on 567 paths from 80 vantage points
  2. Peer of AS18186seen on 7,542 paths from 103 vantage points
  3. Peer of AS7473seen on 4,810 paths from 9 vantage points
  4. Peer of AS8966seen on 133,632 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. Singapore639021818674738966132337Shown above

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

14%

Seen by 11 of 80 full-feed vantage points

Seen by few vantage points

Observed at 3 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
22nd October 2021
Allocation block
176.97.205.0/24
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 176.97.205.0/24
ROA prefixAuthorised originMax length
176.97.205.0/24AS34346/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.205.0/24
PrefixAddressesOriginVisibility
176.97.204.0/24256AS48031Ivanov Vitaliy Sergeevich80/80

History

  1. AS6390212th August 2026 present
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.205.0/24 in the calculator/24 reference

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