subnet.im

2001:8f8:2da0::/44

EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCAS5384

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

2%

1 of 62 vantage points

RPKI

Invalid

Registry

RIPE NCCAE

Allocated 20th September 2002

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 2001:8f8:2da0::/44 as seen from Singapore, read outward from the origin: AS5384 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS5384EMIRATES TELECOMM…OriginAS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. 1AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCAEOrigin
    Peer of AS5384seen on 45,716 paths from 141 vantage points
  2. 2AS8966Etisalat (E&)AE
    Peer of AS8966seen on 133,632 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Singapore53848966132337Shown 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.

Route visibility

2%

Seen by 1 of 62 full-feed vantage points

Seen by few vantage points

Observed at 1 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 September 2002
Allocation block
2001:8f8::/29
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2001:8f8:2da0::/44
ROA prefixAuthorised originMax length
2001:8f8::/32AS8966/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2001:8f8:2da0::/44: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2001:8f8::/32AS89662001:8f8:2da0::/…AS5384This prefix2001:8f8:2db0::/…AS5384

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 2001:8f8:2da0::/44
PrefixAddressesOriginVisibility
2001:8f8::/324.3B × /64AS8966Etisalat (E&)61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2001:8f8:2da0::/44
PrefixAddressesOriginVisibility
2001:8f8:2db0::/441M × /64AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC1/62

History

  1. AS538412th 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.

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