subnet.im

194.132.172.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCSE

Allocated 17th January 1995

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 194.132.172.0/24 as seen from Amsterdam, read outward from the origin: AS57630 → AS5405 → AS8298. Each hop is listed with its network name beneath the graph.AS5763084 Grams ABOriginAS5405Inter.link GmbHAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS57630seen on 5,130 paths from 74 vantage points
  2. Peer of AS5405seen on 2,122 paths from 2 vantage points
  3. 3AS8298IPng 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. Amsterdam5763054058298Shown above
  2. London, UK5763012998529This path
  3. Sao Paulo57630129935280This path
  4. Singapore576301299335623673This path
  5. Oregon, US576305405855142013This 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 76 of 76 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
Sweden
Allocated
17th January 1995
Allocation block
194.132.0.0/16
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 194.132.172.0/24
ROA prefixAuthorised originMax length
194.132.172.0/23AS57630/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 194.132.172.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.194.132.172.0/23AS57630194.132.172.0/24AS57630This prefix194.132.173.0/24AS57630

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 194.132.172.0/24
PrefixAddressesOriginVisibility
194.132.172.0/23512AS5763084 Grams AB76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 194.132.172.0/24
PrefixAddressesOriginVisibility
194.132.173.0/24256AS5763084 Grams AB76/76

History

  1. AS5763028th September 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 194.132.172.0/24 in the calculator/24 reference

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