subnet.im

104.247.212.0/23

At a glance

Addresses

512

/23 block

Visibility

64%

52 of 81 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 9th December 2014

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 104.247.212.0/23 as seen from Oregon, US, read outward from the origin: AS33651 → AS7922 → AS23352 → AS20130. Each hop is listed with its network name beneath the graph.AS33651Comcast Cable Com…OriginAS7922Comcast Cable Com…AS23352DEFT.COMAS20130Depaul University

Seen from Oregon, US

  1. Peer of AS33651seen on 24,930 paths from 145 vantage points
  2. Peer of AS7922seen on 2,028 paths from 1 vantage point
  3. Peer of AS23352seen on 105,332 paths from 1 vantage point
  4. 4AS20130Depaul UniversityUSVantage 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. London, UK33667335635280This path
  2. Sao Paulo33667335635280This path
  3. Amsterdam336673356250918298This path
  4. Singapore3366733568966132337This path
  5. Oregon, US3365179222335220130Shown above

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

64%

Seen by 52 of 81 full-feed vantage points

Partially propagated

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
ARIN — North America
Country
United States
Allocated
9th December 2014
Allocation block
104.247.192.0/19
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 104.247.212.0/23
ROA prefixAuthorised originMax length
104.247.212.0/23AS33651/24
104.247.212.0/23AS33667/24
104.247.212.0/23AS55201/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

Prefixes of the same length sharing a parent block with 104.247.212.0/23
PrefixAddressesOriginVisibility
104.247.214.0/23512AS46261QuickPacket, LLC80/81

History

  1. AS3365122nd September 2026 — present
  2. AS3366722nd 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 104.247.212.0/23 in the calculator/23 reference

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