subnet.im

176.53.37.0/24

AS215567 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

Valid

Registry

RIPE NCCTR

Allocated 26th May 2011

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 176.53.37.0/24 as seen from Oregon, US, read outward from the origin: AS42926 → AS6205 → AS3257 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS42926Radore Veri Merke…OriginAS6205HizliNet Teknoloj…AS3257GTT Communication…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS42926seen on 20,795 paths from 138 vantage points
  2. Peer of AS6205seen on 31,228 paths from 139 vantage points
  3. Peer of AS3257seen on 66,143 paths from 17 vantage points
  4. Peer of AS6762seen on 32,980 paths from 1 vantage point
  5. Peer of AS1680seen on 35,288 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. Oregon, US42926620532576762168042013Shown 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

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
Türkiye
Allocated
26th May 2011
Allocation block
176.53.0.0/17
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.53.37.0/24
ROA prefixAuthorised originMax length
176.53.37.0/24AS215567/24
176.53.37.0/24AS42926/24
176.53.0.0/17AS42926/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.53.37.0/24
PrefixAddressesOriginVisibility
176.53.36.0/24256AS203771SERVERVIA BILISIM YAZILIM VE TELEKOMUNIKASYON HIZMETLERI LIMITED SIRKETI76/76

History

  1. AS429261st November 2026 — present
  2. AS21556731st October 2026 — 31st October 2026
  3. AS4292630th October 2026 — 31st October 2026
  4. AS21556728th October 2026 — 31st October 2026
  5. AS21556722nd September 2026 — 27th October 2026
  6. AS4292612th August 2026 — 21st September 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.53.37.0/24 in the calculator/24 reference

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