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

AS60357 ·

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

Warning: AS60357 (MEGAGROUP-AS) announces 2 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS60357
HolderMEGAGROUP-AS Megagroup.ru LLC
AllocationRIPE NCC, Russia (RU), allocated 2013-08-02
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid0% (0 / 2)
Upstreams and peers11
Peering policyOpen

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

    2 of 2 announced prefixes have no ROA (RPKI not found): 185.32.56.0/23, 185.32.58.0/23.

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

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

    185.32.56.0/23 AS60357 max-length /23
    185.32.58.0/23 AS60357 max-length /23

    Open in RPKI / ROA validator Guide

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS60357 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 185.32.56.0/23, 185.32.58.0/23.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 11 upstreams and peers, 0 downstream networks seen.
HolderMEGAGROUP-AS Megagroup.ru LLC
IPv4 prefixes2
IPv6 prefixes0
RPKI2 not found
Downstream networks0
Routes to fix
PrefixRPKI
185.32.56.0/23 No ROA
185.32.58.0/23 No ROA

Announced prefixes 2

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.
NameMEGAGROUP-AS
HandleAS60357
RangeAS60357
Statusactive
Registered2013-08-02T09:58:01Z
Last changed2023-07-14T14:13:24Z
Abuse contactabuse@megagroup.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2013-08-02
StatusAllocated
Delegated rangeAS60357

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

Contacts
RoleNameEmail
registrant MNT-MEGAGROUP
registrant Megagroup.ru LLC
registrant RIPE-NCC-END-MNT
abuse Megagroup.ru LLC Administrator abuse@megagroup.ru

Source: https://rdap.db.ripe.net/autnum/60357. 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 No public NOC, policy or technical contact.
  • Pass: AS60357 is in PeeringDB as Megagroup.ru LLC.
  • Info: Peering policy: Open.
  • Info: Present at 7 internet exchanges with 7 ports (0M in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkMegagroup.ru LLC
AS numberAS60357
TypeContent, Regional
Websitehttp://megagroup.ru
IRR as-setAS60357
Prefixes (IPv4 / IPv6)10 / 10
TrafficMostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup