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

AS50810 ·

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

Warning: AS50810 (Mobinnet-AS Mobin Net Communication Com…) announces 192 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS50810
HolderMobinnet-AS Mobin Net Communication Company (Private Joint Stock)
AllocationRIPE NCC, Iran (IR), allocated 2010-03-29
Prefixes (IPv4 / IPv6)192 / 0
RPKI valid98% (189 / 192)
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 192 announced prefixes have no ROA (RPKI not found): 91.209.186.0/24, 195.96.32.0/21, 195.96.48.0/20.

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

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

    91.209.186.0/24 AS50810 max-length /24
    195.96.32.0/21 AS50810 max-length /21
    195.96.48.0/20 AS50810 max-length /20

    Open in RPKI / ROA validator Guide

  3. Warning

    48 of 192 announced prefixes have no IRR route object: 178.131.98.0/23, 92.114.26.0/23, 178.131.153.0/24, 178.131.27.0/24, 91.209.186.0/24 (+43).

    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 AS50810 in your RIR’s IRR database (or RADB).

    route: 178.131.98.0/23
    origin: AS50810
    
    route: 92.114.26.0/23
    origin: AS50810
    
    route: 178.131.153.0/24
    origin: AS50810

    Open in ASN & BGP prefix lookup

  4. 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: AS50810 announces 192 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 192 announced prefixes have no ROA (RPKI not found): 91.209.186.0/24, 195.96.32.0/21, 195.96.48.0/20.
  • Info: 189 of 192 announced prefixes are RPKI valid.
  • Warning: 48 of 192 announced prefixes have no IRR route object: 178.131.98.0/23, 92.114.26.0/23, 178.131.153.0/24, 178.131.27.0/24, 91.209.186.0/24 (+43).
  • Info: 2 upstreams and peers, 19 downstream networks seen.
HolderMobinnet-AS Mobin Net Communication Company (Private Joint Stock)
IPv4 prefixes192
IPv6 prefixes0
RPKI189 valid · 3 not found
Without IRR route object48
Downstream networks19
Routes to fix
PrefixRPKI
91.209.186.0/24 No ROA
195.96.32.0/21 No ROA
195.96.48.0/20 No ROA

Upstreams and peers seen to the left 2

Announced prefixes 192

Showing the first 100.

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.
NameMobinnet-AS
HandleAS50810
RangeAS50810
Statusactive
Registered2010-03-29T06:52:50Z
Last changed2026-09-16T06:51:21Z
Abuse contactabuse@mobinnet.net
Allocation
Registry (RIR)RIPE NCC
CountryIran (IR)
Delegated on2010-03-29
StatusAllocated
Delegated rangeAS50810

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

Contacts
RoleNameEmail
registrant MNT-MOBINNET
registrant MOBINNET1-MNT
registrant MOBINNET2-MNT
registrant Mobin Net Communication Company (Private Joint Stock)
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@mobinnet.net

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