subnet.im

179.254.64.0/22

At a glance

Addresses

1,024

/22 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 6th March 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 179.254.64.0/22 as seen from Amsterdam, read outward from the origin: AS400402 → AS394177 → AS137409 → AS8298. Each hop is listed with its network name beneath the graph.AS400402Hosting Bot, LLCOriginAS394177Shift Hosting LLCAS137409GSL Networks Pty …AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS400402seen on 4,351 paths from 144 vantage points
  2. Peer of AS394177seen on 10,990 paths from 144 vantage points
  3. Peer of AS137409seen on 7,188 paths from 2 vantage points
  4. 4AS8298IPng 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. Sao Paulo40040239417735280This path
  2. Amsterdam4004023941771374098298Shown above
  3. London, UK400402394177129935280This path
  4. Singapore400402394177137409132337This path
  5. Oregon, US400402394177693920130This 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
United States
Allocated
6th March 2025
Allocation block
179.254.64.0/18
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 179.254.64.0/22
ROA prefixAuthorised originMax length
179.254.64.0/22AS400402/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

No prefix of the same length in the same parent block is announced.

History

  1. AS40040222nd September 2026 — present
  2. AS40115212th 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 179.254.64.0/22 in the calculator/22 reference

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