subnet.im

66.78.38.0/24

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 26th April 2016

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 66.78.38.0/24 as seen from Oregon, US, read outward from the origin: AS40676 → AS3257 → AS1299 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS40676Psychz NetworksOriginAS3257GTT Communication…AS1299Arelion (fka. Tel…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS40676seen on 29,594 paths from 138 vantage points
  2. Peer of AS3257seen on 225,174 paths from 52 vantage points
  3. Peer of AS1299seen on 321,664 paths from 1 vantage point
  4. Peer of AS8551seen on 1,077,002 paths from 1 vantage 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. Sao Paulo4067635280This path
  2. London, UK4067669398529This path
  3. Amsterdam406762914250918298This path
  4. Oregon, US4067632571299855142013Shown 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

72%

Seen by 55 of 76 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
26th April 2016
Allocation block
66.78.0.0/18
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 66.78.38.0/24
ROA prefixAuthorised originMax length
66.78.38.0/24AS40676/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 66.78.38.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.66.78.0.0/18AS2176966.78.38.0/24AS40676This prefix66.78.39.0/24AS214054

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 66.78.38.0/24
PrefixAddressesOriginVisibility
66.78.0.0/1816.4kAS21769Colocation America Corporation75/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 66.78.38.0/24
PrefixAddressesOriginVisibility
66.78.39.0/24256AS214054Nitrode Corporation trading as ChartVPS Technologies76/76

History

  1. AS406767th November 2026 — present
  2. AS400653rd November 2026 — 6th November 2026
  3. AS204734th October 2026 — 3rd November 2026
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 66.78.38.0/24 in the calculator/24 reference

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