SUBNET.IM

83.111.0.0/17

At a glance

Addresses

32,768

/17 block

Visibility

54%

43 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCAE

Allocated 20th January 2004

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 83.111.0.0/17 as seen from Oregon, US, read outward from the origin: AS5384 → AS8966 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS5384EMIRATES TELECOMM…OriginAS8966Etisalat (E&)AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS5384seen on 45,716 paths from 141 vantage points
  2. Peer of AS8966seen on 1,276 paths from 15 vantage points
  3. Peer of AS6939seen on 975,334 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, UK538489668529This path
  2. Singapore53848966132337This path
  3. Oregon, US53848966693920130Shown above
  4. Sao Paulo8966845232573356266213This path
  5. Amsterdam89668452676217434549213151This 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

54%

Seen by 43 of 80 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United Arab Emirates
Allocated
20th January 2004
Allocation block
83.110.0.0/15
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 83.111.0.0/17
ROA prefixAuthorised originMax length
83.111.0.0/17AS5384/17
83.111.0.0/17AS8966/17
83.111.0.0/16AS5384/16
83.110.0.0/15AS5384/15

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 83.111.0.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.83.111.0.0/16AS538483.110.0.0/15AS538483.111.128.0/17AS538483.111.0.0/17AS5384This prefix83.111.128.0/17AS896683.111.0.0/18AS538483.111.64.0/18AS538483.111.3.0/24AS622083.111.4.0/24AS622083.111.5.0/24AS5384+3 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.

History

  1. AS538412th August 2026 present
  2. AS896612th 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 83.111.0.0/17 in the calculator/17 reference

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