subnet.im

78.41.60.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCIQ

Allocated 17th January 2025

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 78.41.60.0/24 as seen from Amsterdam, read outward from the origin: AS216346 → AS212330 → AS208293 → AS211513 → AS211181 → AS57344 → AS8298. Each hop is listed with its network name beneath the graph.AS216346General Secretari…OriginAS212330Civilisation Info…AS208293AlSalam State Com…AS211513Al Lawn Al Akhdar…AS211181Civilisation Info…AS57344Telehouse EADAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS216346seen on 171 paths from 61 vantage points
  2. Peer of AS212330seen on 29,458 paths from 145 vantage points
  3. Peer of AS208293seen on 15,698 paths from 145 vantage points
  4. Peer of AS211513seen on 3,611 paths from 127 vantage points
  5. Peer of AS211181seen on 12,222 paths from 144 vantage points
  6. Peer of AS57344seen on 1,156 paths from 2 vantage points
  7. 7AS8298IPng Networks GmbHCHVantage 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, US21634620829320017832572335220130This path
  2. Amsterdam216346212330208293211513211181573448298Shown above
  3. London, UK2163462123302082932115132111815734435280This path
  4. Singapore21634621233020829321151321118157344132337This path
  5. Sao Paulo21634621233020829321151321118157344645335280This 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

99%

Seen by 80 of 81 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
Iraq
Allocated
17th January 2025
Allocation block
78.41.60.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 78.41.60.0/24
ROA prefixAuthorised originMax length
78.41.60.0/24AS19905/24
78.41.60.0/24AS208293/24
78.41.60.0/24AS216346/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 78.41.60.0/24
PrefixAddressesOriginVisibility
78.41.61.0/24256AS47603Zirsakht Pishro Abr Damavand Private Joint Stock Company81/81

History

  1. AS1990526th September 2026 — present
  2. AS21634625th September 2026 — present
  3. AS1990522nd September 2026 — 25th September 2026
  4. AS21634612th August 2026 — 22nd 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 78.41.60.0/24 in the calculator/24 reference

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