subnet.im

94.160.128.0/17

WIND TRE S.P.A.AS1267

At a glance

Addresses

32,768

/17 block

Visibility

14%

11 of 80 vantage points

RPKI

Invalid

Registry

RIPE NCCIT

Allocated 7th August 2008

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 1 observed path to 94.160.128.0/17, fanning out from AS1267 toward the vantage points that see it. Each path is written out in full beneath the graph.AS1267WIND TRE S.P.A.OriginAS132337Axclusive
  1. Singapore1267132337This 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.

Route visibility

14%

Seen by 11 of 80 full-feed vantage points

Seen by few vantage points

Observed at 4 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
Italy
Allocated
7th August 2008
Allocation block
94.160.0.0/13
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 94.160.128.0/17
ROA prefixAuthorised originMax length
94.160.0.0/16AS1267/16

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 94.160.128.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.94.160.0.0/16AS126794.160.0.0/13AS2460894.160.128.0/17AS1267This prefix94.160.0.0/17AS1267

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 94.160.128.0/17
PrefixAddressesOriginVisibility
94.160.0.0/1665.5kAS1267WIND TRE S.P.A.80/80
94.160.0.0/13524kAS24608WIND TRE S.P.A.79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 94.160.128.0/17
PrefixAddressesOriginVisibility
94.160.0.0/1732.8kAS1267WIND TRE S.P.A.11/80

History

  1. AS126712th 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 94.160.128.0/17 in the calculator/17 reference

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