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

AS9730 · 

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

Problem: AS9730 (BHARTITELESONIC-AS-IN-AP) announces 6 IPv4 and 2 IPv6 prefixes. 1 problem · 4 warnings

AS pageAS9730
HolderBHARTITELESONIC-AS-IN-AP - Bharti Telesonic Ltd
AllocationAPNIC, India (IN), allocated 2007-09-17
Prefixes (IPv4 / IPv6)6 / 2
RPKI valid38% (3 / 8)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Problem

    3 of 8 announced prefixes are RPKI invalid: 152.52.9.0/24, 182.95.251.0/24, 2401:4900:beff::/48.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 8 announced prefixes have no ROA (RPKI not found): 203.193.178.0/24, 2404:a800:4001::/48.

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

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

    203.193.178.0/24 AS9730 max-length /24
2404:a800:4001::/48 AS9730 max-length /48

    Open in RPKI / ROA validator Guide

  3. Warning

    5 of 8 announced prefixes have no IRR route object: 182.95.251.0/24, 2401:4900:beff::/48, 203.193.178.0/24, 2404:a800:4001::/48, 152.52.9.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 AS9730 in your RIR’s IRR database (or RADB).

    route: 182.95.251.0/24
origin: AS9730

route6: 2401:4900:beff::/48
origin: AS9730

route: 203.193.178.0/24
origin: AS9730

    Open in ASN & BGP prefix lookup

  4. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  5. 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 3 of 8 announced prefixes are RPKI invalid: 152.52.9.0/24, 182.95.251.0/24, 2401:4900:beff::/48.
  • Pass: AS9730 announces 6 IPv4 and 2 IPv6 prefixes.
  • Problem: 3 of 8 announced prefixes are RPKI invalid: 152.52.9.0/24, 182.95.251.0/24, 2401:4900:beff::/48.
  • Warning: 2 of 8 announced prefixes have no ROA (RPKI not found): 203.193.178.0/24, 2404:a800:4001::/48.
  • Info: 3 of 8 announced prefixes are RPKI valid.
  • Warning: 5 of 8 announced prefixes have no IRR route object: 182.95.251.0/24, 2401:4900:beff::/48, 203.193.178.0/24, 2404:a800:4001::/48, 152.52.9.0/24.
  • Info: 2 upstreams and peers, 183 downstream networks seen.
HolderBHARTITELESONIC-AS-IN-AP - Bharti Telesonic Ltd
IPv4 prefixes6
IPv6 prefixes2
RPKI3 valid · 3 invalid · 2 not found
Without IRR route object5
Downstream networks183
Routes to fix
PrefixRPKI
152.52.9.0/24 RPKI invalid
182.95.251.0/24 RPKI invalid
2401:4900:beff::/48 RPKI invalid
203.193.178.0/24 No ROA
2404:a800:4001::/48 No ROA

Upstreams and peers seen to the left 2

AS9498 Bharti Airtel Limited AS64313 NAP Info IPT MAX

Announced prefixes 8

59.144.97.0/24 61.246.50.0/24 152.52.9.0/24 152.52.48.0/24 182.95.251.0/24 203.193.178.0/24 2401:4900:beff::/48 2404:a800:4001::/48

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameBHARTITELESONIC-AS-IN-AP
HandleAS9730
RangeAS9730
CountryIN
Statusactive
Registered2008-09-04T06:40:43Z
Last changed2020-07-07T05:00:50Z
Abuse contactShankar.B@airtel.com
Allocation
Registry (RIR)APNIC
CountryIndia (IN)
Delegated on2007-09-17
StatusAllocated
Delegated rangeAS9730

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

Contacts
RoleNameEmail
administrative, technical Shailesh Gupta apnic@bhartitelesonic.com
registrant Bharti Airtel Limited apnic@airtel.com
abuse IRT-BHARTITELESONIC-IN Shankar.B@airtel.com

Source: https://rdap.apnic.net/autnum/9730. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS9730 is in PeeringDB as Bharti Airtel AS9730.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-06-16.
NetworkBharti Airtel AS9730
AS numberAS9730
TypeEnterprise, Not Disclosed
Websitehttp://www.airtel.in
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-06-16

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup