subnet.im

104.167.96.0/19

COMMNET WIRELESS LLCAS19256

SWC TELESOLUTIONS, INC.AS394991

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

ARINUS

Allocated 9th December 2020

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 104.167.96.0/19 as seen from London, UK, read outward from the origin: AS19256 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS19256COMMNET WIRELESS …OriginAS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS19256COMMNET WIRELESS LLCUSOrigin
    Peer of AS19256seen on 1,587 paths from 142 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 45,429 paths from 12 vantage points
  3. 3AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam192566939213151This path
  2. London, UK1925669398529Shown above
  3. Sao Paulo192566939266213This path
  4. Singapore192566939132337This path
  5. Oregon, US19256693920130This 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
ARIN — North America
Country
United States
Allocated
9th December 2020
Allocation block
104.167.96.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 104.167.96.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.104.167.96.0/19AS19256This prefix104.167.100.0/22AS394991104.167.104.0/22AS394991104.167.108.0/22AS394991104.167.112.0/22AS394991104.167.116.0/22AS394991+5 more

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.

Sibling prefixes

Prefixes of the same length sharing a parent block with 104.167.96.0/19
PrefixAddressesOriginVisibility
104.167.64.0/198.2kAS22552eSited Solutions79/80

History

  1. AS1925612th August 2026 — present
  2. AS39499112th 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 104.167.96.0/19 in the calculator/19 reference

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