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

AS52060 · 

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

Warning: AS52060 (MAXIMATELECOM-SPB-AS) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS52060
HolderMAXIMATELECOM-SPB-AS "MaximaTelecom North-West" LLC
AllocationRIPE NCC, Russia (RU), allocated 2010-12-22
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
Upstreams and peers17
Peering policySelective

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

    4 of 4 announced prefixes have no ROA (RPKI not found): 81.200.120.0/22, 81.200.120.0/24, 81.200.121.0/24, 81.200.123.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 AS52060 and a max length equal to the prefix length:

    81.200.120.0/22 AS52060 max-length /22
81.200.120.0/24 AS52060 max-length /24
81.200.121.0/24 AS52060 max-length /24
81.200.123.0/24 AS52060 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    3 of 4 announced prefixes have no IRR route object: 81.200.123.0/24, 81.200.120.0/24, 81.200.121.0/24.

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

    route: 81.200.123.0/24
origin: AS52060

route: 81.200.120.0/24
origin: AS52060

route: 81.200.121.0/24
origin: AS52060

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS52060 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 81.200.120.0/22, 81.200.120.0/24, 81.200.121.0/24, 81.200.123.0/24.
  • Warning: 3 of 4 announced prefixes have no IRR route object: 81.200.123.0/24, 81.200.120.0/24, 81.200.121.0/24.
  • Info: 17 upstreams and peers, 0 downstream networks seen.
HolderMAXIMATELECOM-SPB-AS "MaximaTelecom North-West" LLC
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Without IRR route object3
Downstream networks0
Routes to fix
PrefixRPKI
81.200.120.0/22 No ROA
81.200.120.0/24 No ROA
81.200.121.0/24 No ROA
81.200.123.0/24 No ROA

Upstreams and peers seen to the left 17

AS12389 Rostelecom AS31133 MegaFon AS8359 Mobile TeleSystems PJSC AS57304 RETNRU AS25091 IP-Max SA AS47692 Nessus GmbH AS49434 FBW Networks AS50629 LWLcom AS50673 Serverius AS15958 CETIN Ltd. Belgrade AS21030 Docker AS56911 WARIAN

Announced prefixes 4

81.200.120.0/22 81.200.120.0/24 81.200.121.0/24 81.200.123.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.
NameMAXIMATELECOM-SPB-AS
HandleAS52060
RangeAS52060
Statusactive
Registered2010-12-22T09:18:15Z
Last changed2026-01-29T12:53:10Z
Abuse contactnoc-spb@maxima.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2010-12-22
StatusAllocated
Delegated rangeAS52060

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

Contacts
RoleNameEmail
registrant lir-ru-maximatelecom1-1-MNT
registrant "MaximaTelecom North-West" LLC
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role noc-spb@maxima.ru

Source: https://rdap.db.ripe.net/autnum/52060. 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 AS52060 is in PeeringDB as MaximaTelecom.
  • Pass: AS52060 is in PeeringDB as MaximaTelecom.
  • Info: Peering policy: Selective.
  • Info: Present at 3 internet exchanges with 3 ports (30G in total).
  • Info: The record was last updated 2022-07-27.
NetworkMaximaTelecom
AS numberAS52060
TypeNSP, Regional
Websitehttps://www.maximatelecom.ru
IRR as-setRIPE::AS-MAXIMA
Prefixes (IPv4 / IPv6)4 / 0
Traffic5-10Gbps, Heavy Inbound
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27
Contacts
NOCnetworks@maximatelecom.ru

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup