83.111.0.0/17
EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCAS5384
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/17 block
Visibility
43 of 80 vantage points
RPKI
Registry
Allocated 20th January 2004
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS5384seen on 45,716 paths from 141 vantage points
- Peer of AS8966seen on 4,911 paths from 2 vantage points
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
- London, UK538489668529Shown above
- Singapore53848966132337This path
- Oregon, US53848966693920130This path
- Sao Paulo8966845232573356266213This path
- 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 propagatedObserved 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.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 83.111.0.0/16 | 65.5k | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 80/80 |
| 83.110.0.0/15 | 131k | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 80/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 83.111.0.0/18 | 16.4k | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 80/80 |
| 83.111.64.0/18 | 16.4k | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 80/80 |
| 83.111.3.0/24 | 256 | AS6220inContact Inc. | 5/80 |
| 83.111.4.0/24 | 256 | AS6220inContact Inc. | 5/80 |
| 83.111.5.0/24 | 256 | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 5/80 |
| 83.111.6.0/24 | 256 | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 5/80 |
| 83.111.28.0/24 | 256 | AS19905Arbor Cloud | 79/80 |
| 83.111.91.0/24 | 256 | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 5/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 83.111.128.0/17 | 32.8k | AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | 43/80 |
| 83.111.128.0/17 | 32.8k | AS8966Etisalat (E&) | 37/80 |
History
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.