Autonomous system
AS18101 RELIANCE-COMMUNICATIONS-IN Reliance Communications Ltd.DAKC MUMBAI
Unclassified ARIN NSP
Summary
Reliance Communications
mobile telecom enterprise india
RELIANCE-COMMUNICATIONS-IN is held by Reliance Communications Limited.
What it's used for
- The address space carries mobile and enterprise services, evidenced by netnames such as
RCOM,RCOM-Static-DIA, andRCOM-Static-IDC. - The AS announces 529,408 IPv4 addresses across 414 prefixes and 79 IPv6 prefixes, with 22 observed neighbours, indicating a large access network serving end-users and corporate clients.
Notable
- Registrants consistently identify as
Reliance Communications LimitedorIRT-RELIANCE-COMMUNICATIONS-IN, aligning with the AS holder. - Reliance Communications filed for bankruptcy in February 2019, marking a significant shift in the operator's status.
- The inventory is finely subdivided into numerous /19 and /20 blocks, reflecting site-by-site segmentation typical of a large telecommunications provider.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 410 prefixes · 529K addresses IPv6 79 prefixes
| Country | Name | Prefixes |
|---|---|---|
| IN | India | 489 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS18101- Registry name
- RELIANCE-COMMUNICATIONS-IN
- Registrant
- Reliance Communications Limited
- Abuse contact
- Antiabuse.Support@rcom.co.in
- Registered
- 2008-09-04
- Last changed
- 2021-01-13
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Reliance Communications
- Network type
- NSP
- Scope
- Asia Pacific
- Traffic ratio
- Balanced
- Peering policy
- Selective
- IRR as-set
AS-RELIANCE- Facilities
- 2 facilities
- Website
- http://www.rcom.co.in
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 631 valid, 0 with no ROA
- ROAs
- 580 authorising AS18101
- ASPA
- no ASPA record
- IRR
- 100% registered · 631 of 631 announcements
- Route objects
- 5,595 naming AS18101
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 440 networks and 1,773 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere