subnet.im

176.28.76.0/24

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

At a glance

Addresses

256

/24 block

Visibility

29%

22 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCIQ

Allocated 20th May 2011

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.28.76.0/24 as seen from Singapore, read outward from the origin: AS197893 → AS203214 → AS208293 → AS60051 → AS6453 → AS3491 → AS23673. Each hop is listed with its network name beneath the graph.AS197893Elsuhd Company fo…OriginAS203214Hulum Almustakbal…AS208293AlSalam State Com…AS60051Earthlink Telecom…AS6453TATA Communicatio…AS3491PCCW Global (HK) …AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS197893seen on 120 paths from 76 vantage points
  2. Peer of AS203214seen on 67,577 paths from 139 vantage points
  3. Peer of AS208293seen on 81,919 paths from 139 vantage points
  4. Peer of AS60051seen on 16,231 paths from 104 vantage points
  5. Peer of AS6453seen on 248,280 paths from 17 vantage points
  6. Peer of AS3491seen on 86,654 paths from 2 vantage points

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. Singapore197893203214208293600516453349123673Shown above
  2. Oregon, US1978932032142082936005164536762168042013This 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

29%

Seen by 22 of 76 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Iraq
Allocated
20th May 2011
Allocation block
176.28.76.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.28.76.0/24
ROA prefixAuthorised originMax length
176.28.76.0/24AS197893/24
176.28.76.0/24AS19905/24
176.28.76.0/24AS50597/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.28.76.0/24
PrefixAddressesOriginVisibility
176.28.77.0/24256AS197390Al Marafaa Co. for General Trading, Services, Information Technology and Contracts Ltd.75/76

History

  1. AS1978935th November 2026 — present
  2. AS505978th November 2026 — 10th November 2026
  3. AS505975th November 2026 — 5th November 2026
  4. AS19789312th August 2026 — 5th November 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.28.76.0/24 in the calculator/24 reference

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