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

AS206805 ·

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

Warning: AS206805 (T1CLOUD-AS LLC "T1Cloud") announces 41 IPv4 and 3 IPv6 prefixes. 3 warnings

AS pageAS206805
HolderT1CLOUD-AS LLC "T1Cloud"
AllocationRIPE NCC, Russia (RU), allocated 2016-11-02
Prefixes (IPv4 / IPv6)41 / 3
RPKI valid98% (43 / 44)
Upstreams and peers22
Peering policyOpen

What to fix

  1. Warning

    1 of 44 announced prefixes have no ROA (RPKI not found): 130.49.132.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 AS206805 and a max length equal to the prefix length:

    130.49.132.0/24 AS206805 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    3 of 44 announced prefixes have no IRR route object: 203.81.208.0/21, 203.81.220.0/24, 2a0c:ee00:500::/40.

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

    route: 203.81.208.0/21
    origin: AS206805
    
    route: 203.81.220.0/24
    origin: AS206805
    
    route6: 2a0c:ee00:500::/40
    origin: AS206805

    Open in ASN & BGP prefix lookup

  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 1 of 44 announced prefixes have no ROA (RPKI not found): 130.49.132.0/24.
  • Pass: AS206805 announces 41 IPv4 and 3 IPv6 prefixes.
  • Warning: 1 of 44 announced prefixes have no ROA (RPKI not found): 130.49.132.0/24.
  • Info: 43 of 44 announced prefixes are RPKI valid.
  • Warning: 3 of 44 announced prefixes have no IRR route object: 203.81.208.0/21, 203.81.220.0/24, 2a0c:ee00:500::/40.
  • Info: 22 upstreams and peers, 0 downstream networks seen.
HolderT1CLOUD-AS LLC "T1Cloud"
IPv4 prefixes41
IPv6 prefixes3
RPKI43 valid · 1 not found
Without IRR route object3
Downstream networks0
Routes to fix
PrefixRPKI
130.49.132.0/24 No ROA

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.
NameT1CLOUD-AS
HandleAS206805
RangeAS206805
Statusactive
Registered2016-11-02T13:37:59Z
Last changed2025-06-16T14:54:48Z
Abuse contactabuse@ts-cloud.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2016-11-02
StatusAllocated
Delegated rangeAS206805

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

Contacts
RoleNameEmail
registrant LLC "T1Cloud"
registrant RIPE-NCC-END-MNT
registrant T1CLOUD-AS-MNT
abuse Abuse-C Role abuse@ts-cloud.ru

Source: https://rdap.db.ripe.net/autnum/206805. 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: AS206805 is in PeeringDB as T1Cloud.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 4 ports (40G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2024-09-06.
NetworkT1Cloud (LLC "T1Cloud", Т1 Облако)
AS numberAS206805
TypeEnterprise, Regional
Websitehttp://t1-cloud.ru
IRR as-setAS-SET-TCLOUD
Prefixes (IPv4 / IPv6)31 / 4
Traffic5-10Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Looking glasshttps://lg.t1-cloud.ru
Last updated2024-09-06

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup