subnet.im

188.124.28.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 19th June 2009

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 188.124.28.0/24 as seen from Amsterdam, read outward from the origin: AS44565 → AS15924 → AS3257 → AS34549 → AS213151. Each hop is listed with its network name beneath the graph.AS44565VITAL TEKNOLOJI T…OriginAS15924Vodafone TurkeyAS3257GTT Communication…AS34549meerfarbig GmbH &…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS44565seen on 960 paths from 80 vantage points
  2. Peer of AS15924seen on 22,560 paths from 142 vantage points
  3. Peer of AS3257seen on 96,683 paths from 3 vantage points
  4. Peer of AS34549seen on 716,762 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage 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. London, UK445651592467628529This path
  2. Amsterdam4456515924325734549213151Shown above
  3. Sao Paulo445651592432573356266213This path
  4. Singapore445651592412731299132337This path
  5. Oregon, US44565159246762693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

Observed at 5 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
19th June 2009
Allocation block
188.124.0.0/19
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 188.124.28.0/24
ROA prefixAuthorised originMax length
188.124.28.0/24AS44565/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 188.124.28.0/24
PrefixAddressesOriginVisibility
188.124.29.0/24256AS44565VITAL TEKNOLOJI TELEKOMUNIKASYON BILGISAYAR HIZMETLERI VE SANAYI TICARET LTD SIRKETI80/80

History

  1. AS4456512th 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 188.124.28.0/24 in the calculator/24 reference

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