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

AS25122 ·

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

Warning: AS25122 (Gulfsat_Communications-AS GULFSATCOMMUN…) announces 31 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS25122
HolderGulfsat_Communications-AS GULFSATCOMMUNICATIONS COMPANY K.S.C.
AllocationRIPE NCC, Kuwait (KW), allocated 2002-07-31
Prefixes (IPv4 / IPv6)31 / 2
RPKI valid15% (5 / 33)
Upstreams and peers9

What to fix

  1. Warning

    10 of 33 announced prefixes have no ROA (RPKI not found): 194.126.32.0/23, 194.126.32.0/24, 194.126.35.0/24, 194.126.36.0/23, 194.126.36.0/24 (+5).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS25122 and a max length equal to the prefix length:

    194.126.32.0/23 AS25122 max-length /23
    194.126.32.0/24 AS25122 max-length /24
    194.126.35.0/24 AS25122 max-length /24
    194.126.36.0/23 AS25122 max-length /23
    194.126.36.0/24 AS25122 max-length /24
    194.126.37.0/24 AS25122 max-length /24
    194.126.38.0/23 AS25122 max-length /23
    194.126.39.0/24 AS25122 max-length /24
    194.126.40.0/24 AS25122 max-length /24
    194.126.41.0/24 AS25122 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 33 announced prefixes have no IRR route object: 194.126.33.0/24, 2a03:5780:197::/48.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS25122 in your RIR’s IRR database (or RADB).

    route: 194.126.33.0/24
    origin: AS25122
    
    route6: 2a03:5780:197::/48
    origin: AS25122

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 33 announced prefixes have no ROA (RPKI not found): 194.126.32.0/23, 194.126.32.0/24, 194.126.35.0/24, 194.126.36.0/23, 194.126.36.0/24 (+5).
  • Pass: AS25122 announces 31 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 33 announced prefixes have no ROA (RPKI not found): 194.126.32.0/23, 194.126.32.0/24, 194.126.35.0/24, 194.126.36.0/23, 194.126.36.0/24 (+5).
  • Info: 5 of 33 announced prefixes are RPKI valid.
  • Info: The RPKI state of 18 prefixes was not looked up (no ROA of AS25122 covers them; only the first 10 are checked).
  • Warning: 2 of 33 announced prefixes have no IRR route object: 194.126.33.0/24, 2a03:5780:197::/48.
  • Info: 9 upstreams and peers, 0 downstream networks seen.
HolderGulfsat_Communications-AS GULFSATCOMMUNICATIONS COMPANY K.S.C.
IPv4 prefixes31
IPv6 prefixes2
RPKI5 valid · 10 not found · 18 not looked up
Without IRR route object2
Downstream networks0
Routes to fix

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.
NameGulfsat_Communications-AS
HandleAS25122
RangeAS25122
Statusactive
Registered2002-07-31T11:56:43Z
Last changed2018-09-04T09:54:56Z
Abuse contactabuse@gulfsat.com
Allocation
Registry (RIR)RIPE NCC
CountryKuwait (KW)
Delegated on2002-07-31
StatusAllocated
Delegated rangeAS25122

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

Contacts
RoleNameEmail
registrant Gulfsat_Communications-MNT
registrant GULFSATCOMMUNICATIONS COMPANY K.S.C.
registrant RIPE-NCC-END-MNT
abuse IP Operators abuse@gulfsat.com

Source: https://rdap.db.ripe.net/autnum/25122. 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