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

AS34974 ·

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

Warning: AS34974 (KAMCHATKA-AS) announces 13 IPv4 and 0 IPv6 prefixes. 2 warnings

AS pageAS34974
HolderKAMCHATKA-AS PJSC Rostelecom
AllocationRIPE NCC, Russia (RU), allocated 2005-05-11
Prefixes (IPv4 / IPv6)13 / 0
RPKI valid100% (13 / 13)
Upstreams and peers1

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

    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: AS34974 announces 13 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 13 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS12389): an outage there takes the whole network off the internet.
HolderKAMCHATKA-AS PJSC Rostelecom
IPv4 prefixes13
IPv6 prefixes0
RPKI13 valid
Downstream networks0

Upstreams and peers seen to the left 1

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.
NameKAMCHATKA-AS
HandleAS34974
RangeAS34974
Statusactive
Registered2005-05-11T08:33:16Z
Last changed2024-05-27T05:48:04Z
Abuse contactabuse@rt.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2005-05-11
StatusAllocated
Delegated rangeAS34974

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

Contacts
RoleNameEmail
registrant KAMCHATKA-NOC-MNT
registrant PJSC Rostelecom
registrant RIPE-NCC-END-MNT
registrant ROSTELECOM-MNT
abuse PJSC Rostelecom Technical Team abuse@rt.ru

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