SUBNET.IM

67.44.48.0/22

At a glance

Addresses

1,024

/22 block

Visibility

84%

67 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 4th March 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. London, UK66211374098529This path
  2. Singapore66216939132337This path
  3. Oregon, US6621693920130This path
  4. Sao Paulo6306270183356266213This path
  5. Amsterdam63062701817434549213151This 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

84%

Seen by 67 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
4th March 2004
Allocation block
67.44.0.0/14
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 67.44.48.0/22
ROA prefixAuthorised originMax length
67.44.48.0/20AS63062/22
67.44.48.0/20AS6621/22
67.44.0.0/17AS6621/17

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 67.44.48.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.67.44.48.0/20AS6306267.44.48.0/20AS662167.44.48.0/22AS63062This prefix

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 67.44.48.0/22
PrefixAddressesOriginVisibility
67.44.48.0/204.1kAS63062Hughes Network Systems, LLC34/80
67.44.48.0/204.1kAS6621Hughes Network Systems, LLC45/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS6306212th August 2026 present
  2. AS662112th 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 67.44.48.0/22 in the calculator/22 reference

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