Registration
IPv4 Prefixes
32 prefixes · 8,448 addresses Routing data as of 2026-10-07 16:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 202.41.0.0/23 | 202.41.0.0 – 202.41.1.255 | 512 |
| 202.53.64.0/24 | 202.53.64.0 – 202.53.64.255 | 256 |
| 202.53.65.0/24 | 202.53.65.0 – 202.53.65.255 | 256 |
| 202.53.66.0/24 | 202.53.66.0 – 202.53.66.255 | 256 |
| 202.53.67.0/24 | 202.53.67.0 – 202.53.67.255 | 256 |
| 202.53.68.0/24 | 202.53.68.0 – 202.53.68.255 | 256 |
| 202.53.69.0/24 | 202.53.69.0 – 202.53.69.255 | 256 |
| 202.53.71.0/24 | 202.53.71.0 – 202.53.71.255 | 256 |
| 202.53.72.0/24 | 202.53.72.0 – 202.53.72.255 | 256 |
| 202.53.73.0/24 | 202.53.73.0 – 202.53.73.255 | 256 |
| 202.53.74.0/24 | 202.53.74.0 – 202.53.74.255 | 256 |
| 202.53.75.0/24 | 202.53.75.0 – 202.53.75.255 | 256 |
| 202.53.76.0/24 | 202.53.76.0 – 202.53.76.255 | 256 |
| 202.53.77.0/24 | 202.53.77.0 – 202.53.77.255 | 256 |
| 202.53.78.0/24 | 202.53.78.0 – 202.53.78.255 | 256 |
| 202.53.79.0/24 | 202.53.79.0 – 202.53.79.255 | 256 |
| 202.53.80.0/24 | 202.53.80.0 – 202.53.80.255 | 256 |
| 202.53.81.0/24 | 202.53.81.0 – 202.53.81.255 | 256 |
| 202.53.82.0/24 | 202.53.82.0 – 202.53.82.255 | 256 |
| 202.53.83.0/24 | 202.53.83.0 – 202.53.83.255 | 256 |
| 202.53.84.0/24 | 202.53.84.0 – 202.53.84.255 | 256 |
| 202.53.85.0/24 | 202.53.85.0 – 202.53.85.255 | 256 |
| 202.53.86.0/24 | 202.53.86.0 – 202.53.86.255 | 256 |
| 202.53.87.0/24 | 202.53.87.0 – 202.53.87.255 | 256 |
| 202.53.88.0/24 | 202.53.88.0 – 202.53.88.255 | 256 |
| 202.53.89.0/24 | 202.53.89.0 – 202.53.89.255 | 256 |
| 202.53.90.0/24 | 202.53.90.0 – 202.53.90.255 | 256 |
| 202.53.91.0/24 | 202.53.91.0 – 202.53.91.255 | 256 |
| 202.53.92.0/24 | 202.53.92.0 – 202.53.92.255 | 256 |
| 202.53.93.0/24 | 202.53.93.0 – 202.53.93.255 | 256 |
| 202.53.94.0/24 | 202.53.94.0 – 202.53.94.255 | 256 |
| 202.53.95.0/24 | 202.53.95.0 – 202.53.95.255 | 256 |
IPv6 Prefixes
1 prefix · 65,536 × /48 Routing data as of 2026-10-07 16:00 UTC
| Prefix | Addresses |
|---|---|
| 2404:3f00:: | 296 |
BGP Neighbours
9 unique neighbours · 5 upstream/peer · 0 downstream · 4 collector-only. A neighbour can be seen on more than one side. Rows are ordered by AS paths: the number of BGP paths seen by RIPE RIS that contain the adjacency. Sightings count each IPv4/IPv6 route with the adjacency once per RIS peer that sees it (routes × peers), so they show how widely it is seen, not how many distinct routes it carries. Networks seen to the left of this AS in BGP paths, toward the route collectors — typically its transit providers (upstreams) and peers. Networks seen to the left of this AS only when they peer directly with a RIPE RIS route collector, so the adjacency may be an artefact of that peering; many of them also appear on the downstream side. Upstream & peer side (5)
Collector-only (4)
Raw RDAP Response
{
"rdapConformance": [
"history_version_0",
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"notices": [
{
"title": "Source",
"description": [
"Objects returned came from source",
"APNIC"
]
},
{
"title": "Terms and Conditions",
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format."
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/10225",
"rel": "terms-of-service",
"href": "http://www.apnic.net/db/dbcopyright.html",
"type": "text/html"
}
]
},
{
"title": "Whois Inaccuracy Reporting",
"description": [
"If you see inaccuracies in the results, please visit: "
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/10225",
"rel": "inaccuracy-report",
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"type": "text/html"
}
]
}
],
"country": "IN",
"name": "NETTLINX-IN-AP",
"status": [
"active"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T06:40:29Z"
},
{
"eventAction": "last changed",
"eventDate": "2024-01-16T08:09:46Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/10225",
"rel": "self",
"href": "https://rdap.apnic.net/autnum/10225",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"Nettlinx Limited"
],
"title": "description"
}
],
"entities": [
{
"roles": [
"abuse"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2011-01-20T06:48:39Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-09-26T06:23:18Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/10225",
"rel": "self",
"href": "https://rdap.apnic.net/entity/IRT-NETTLINX-IN",
"type": "application/rdap+json"
}
],
"handle": "IRT-NETTLINX-IN",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-NETTLINX-IN"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "NETTLINX Limited,\n3rd Floor, My Home Sarovar Complex,\nSecratriat road, Saifabad, Hyderabad - 500 004"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
},
{
"roles": [
"administrative"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T07:29:15Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-09-27T09:34:24Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/10225",
"rel": "self",
"href": "https://rdap.apnic.net/entity/MLR1-AP",
"type": "application/rdap+json"
}
],
"handle": "MLR1-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
}
],
"handle": "AS10225",
"startAutnum": 10225,
"endAutnum": 10225,
"objectClassName": "autnum",
"port43": "whois.apnic.net"
} Contact details of private individuals are redacted.