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

AS43378 · 

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

Warning: AS43378 (MoCISA Ministry of Commerce and Industr…) announces 3 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS43378
HolderMoCISA Ministry of Commerce and Industry in Saudi Arabia
AllocationRIPE NCC, Saudi Arabia (SA), allocated 2011-01-12
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid0% (0 / 3)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    3 of 3 announced prefixes have no ROA (RPKI not found): 91.221.184.0/23, 91.221.184.0/24, 91.221.185.0/24.

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

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

    91.221.184.0/23 AS43378 max-length /23
91.221.184.0/24 AS43378 max-length /24
91.221.185.0/24 AS43378 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS43378 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 91.221.184.0/23, 91.221.184.0/24, 91.221.185.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderMoCISA Ministry of Commerce and Industry in Saudi Arabia
IPv4 prefixes3
IPv6 prefixes0
RPKI3 not found
Downstream networks0
Routes to fix
PrefixRPKI
91.221.184.0/23 No ROA
91.221.184.0/24 No ROA
91.221.185.0/24 No ROA

Upstreams and peers seen to the left 2

AS35753 Integrated Telecom (ITC) AS48695 Etihad Atheeb Telecom /GO Telecom

Announced prefixes 3

91.221.184.0/23 91.221.184.0/24 91.221.185.0/24

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.
NameMoCISA
HandleAS43378
RangeAS43378
Statusactive
Registered2011-01-12T14:33:01Z
Last changed2025-12-01T11:37:50Z
Abuse contactMswayeh@mci.gov.sa
Allocation
Registry (RIR)RIPE NCC
CountrySaudi Arabia (SA)
Delegated on2011-01-12
StatusAllocated
Delegated rangeAS43378

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

Contacts
RoleNameEmail
registrant MOBILY-MNT
registrant Ministry of Commerce and Industry in Saudi Arabia
registrant RIPE-NCC-END-MNT
abuse Abuse Contact Mswayeh@mci.gov.sa

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