Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS8959 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS8959"
JSON Docs

Warning: AS8959 (EMIRATES) announces nothing right now. 1 warning

AS pageAS8959
HolderEMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC
AllocationRIPE NCC, United Arab Emirates (AE), allocated 1998-09-03
Prefixes (IPv4 / IPv6)0 / 0

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS8959 is not announcing anything right now.
  • Info: AS8959 is not announcing anything right now.
HolderEMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC
IPv4 prefixes0
IPv6 prefixes0
Downstream networks0

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameUNSPECIFIED
HandleAS8959
RangeAS8959
Statusactive
Registered1970-01-01T00:00:00Z
Last changed2017-11-15T09:13:07Z
Abuse contactabuse@emirates.net.ae
Allocation
Registry (RIR)RIPE NCC
CountryUnited Arab Emirates (AE)
Delegated on1998-09-03
StatusAllocated
Delegated rangeAS8959

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant ETISALAT-MNT
registrant EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC
registrant RIPE-NCC-END-MNT
abuse ETISALAT Abuse Handling abuse@emirates.net.ae

Source: https://rdap.db.ripe.net/autnum/8959. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup