subnet.im

139.140.0.0/16

At a glance

Addresses

65,536

/16 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 16th March 1990

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.

OriginVantage points
AS path graph: 5 observed paths to 139.140.0.0/16, fanning out from AS22847 toward the vantage points that see it. Each path is written out in full beneath the graph.AS22847Bowdoin CollegeOriginAS5760Biddeford Interne…AS6939Hurricane Electri…AS213151Christian ElsenAS13536FirstLight Networ…AS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS20130Depaul University
  1. Amsterdam2284757606939213151This path
  2. London, UK228471353612998529This path
  3. Sao Paulo2284757606939266213This path
  4. Singapore2284757606939132337This path
  5. Oregon, US228475760693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally 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
16th March 1990
Allocation block
139.140.0.0/16
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 139.140.0.0/16
ROA prefixAuthorised originMax length
139.140.0.0/16AS22847/17

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 139.140.0.0/16: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.139.140.0.0/16AS22847This prefix139.140.0.0/17AS22847139.140.128.0/17AS22847

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

Announcements contained within 139.140.0.0/16
PrefixAddressesOriginVisibility
139.140.0.0/1732.8kAS22847Bowdoin College80/80
139.140.128.0/1732.8kAS22847Bowdoin College80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 139.140.0.0/16
PrefixAddressesOriginVisibility
139.141.0.0/1665.5kAS25242KUWAIT UNIVERSITY80/80

History

  1. AS2284712th 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 139.140.0.0/16 in the calculator/16 reference

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