SUBNET.IM

84.17.192.0/19

Advania Sverige ABAS57208

Advania Sverige ABAS58343

Announced by more than one origin AS (MOAS).

At a glance

Addresses

8,192

/19 block

Visibility

81%

65 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCSE

Allocated 3rd August 2004

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.

  1. Oregon, US5834357208693920130This path
  2. Amsterdam572085834357208129934549213151This path
  3. London, UK572085834357208125764538529This path
  4. Sao Paulo57208583435720812993356266213This path
  5. Singapore5720858343572081257174132337This 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

81%

Seen by 65 of 80 full-feed vantage points

Partially 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
3rd August 2004
Allocation block
84.17.192.0/19
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 84.17.192.0/19: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.84.17.192.0/19AS57208This prefix84.17.193.0/24AS5720884.17.204.0/24AS5720884.17.205.0/24AS5720884.17.220.0/24AS5720884.17.221.0/24AS57208

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

No less specific announcement covers this prefix.

More specific announcements

Sibling prefixes

Prefixes of the same length sharing a parent block with 84.17.192.0/19
PrefixAddressesOriginVisibility
84.17.224.0/198.2kAS16256MTS PJSC80/80

History

  1. AS5834312th August 2026 present
  2. AS5720812th 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 84.17.192.0/19 in the calculator/19 reference

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