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

AS47502 · 

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

Warning: AS47502 (OPTIMATELECOM-AS) announces nothing right now. 1 warning

AS pageAS47502
HolderOPTIMATELECOM-AS Optima-Telecom LLC
AllocationRIPE NCC, Russia (RU), allocated 2023-09-15
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 AS47502 is not announcing anything right now.
  • Info: AS47502 is not announcing anything right now.
HolderOPTIMATELECOM-AS Optima-Telecom LLC
IPv4 prefixes0
IPv6 prefixes0
Downstream networks1

Upstreams and peers seen to the left 2

AS57304 RETNRU AS9002 RETN

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.
NameOPTIMATELECOM-AS
HandleAS47502
RangeAS47502
Statusactive
Registered2023-09-15T11:04:04Z
Last changed2025-12-30T08:15:02Z
Abuse contactabuse@optima-telecom.com
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2023-09-15
StatusAllocated
Delegated rangeAS47502

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

Contacts
RoleNameEmail
registrant OPTIMA-TELECOM-MNT
registrant Optima-Telecom LLC
registrant RIPE-NCC-END-MNT
abuse Optima-Telecom LLC abuse@optima-telecom.com

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