Registration
IPv4 Prefixes
22 prefixes · 8,960 addresses · 5 top-level Routing data as of 2026-10-08 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 202.123.224.0/24 | 202.123.224.0 – 202.123.224.255 | 256 |
| 202.123.236.0/24 | 202.123.236.0 – 202.123.236.255 | 256 |
| 202.123.237.0/24 | 202.123.237.0 – 202.123.237.255 | 256 |
| 202.127.96.0/20 | 202.127.96.0 – 202.127.111.255 | 4,096 |
| 202.127.96.0/24 | 202.127.96.0 – 202.127.96.255 | 256 |
| 202.127.97.0/24 | 202.127.97.0 – 202.127.97.255 | 256 |
| 202.127.98.0/24 | 202.127.98.0 – 202.127.98.255 | 256 |
| 202.127.99.0/24 | 202.127.99.0 – 202.127.99.255 | 256 |
| 202.127.100.0/24 | 202.127.100.0 – 202.127.100.255 | 256 |
| 202.127.101.0/24 | 202.127.101.0 – 202.127.101.255 | 256 |
| 202.127.102.0/24 | 202.127.102.0 – 202.127.102.255 | 256 |
| 202.127.103.0/24 | 202.127.103.0 – 202.127.103.255 | 256 |
| 202.127.104.0/24 | 202.127.104.0 – 202.127.104.255 | 256 |
| 202.127.105.0/24 | 202.127.105.0 – 202.127.105.255 | 256 |
| 202.127.106.0/24 | 202.127.106.0 – 202.127.106.255 | 256 |
| 202.127.107.0/24 | 202.127.107.0 – 202.127.107.255 | 256 |
| 202.127.108.0/24 | 202.127.108.0 – 202.127.108.255 | 256 |
| 202.127.109.0/24 | 202.127.109.0 – 202.127.109.255 | 256 |
| 202.127.110.0/24 | 202.127.110.0 – 202.127.110.255 | 256 |
| 202.127.111.0/24 | 202.127.111.0 – 202.127.111.255 | 256 |
| 210.79.208.0/20 | 210.79.208.0 – 210.79.223.255 | 4,096 |
| 210.79.217.0/24 | 210.79.217.0 – 210.79.217.255 | 256 |
IPv6 Prefixes
This AS does not currently announce any IPv6 prefixes.
BGP Neighbours
4 unique neighbours · 3 upstream/peer · 1 downstream · 1 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 right of this AS in BGP paths — networks whose routes it carries, typically its customers (downstreams). 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 (3)
Downstream side (1)
AS Name AS paths IPv4 sightings IPv6 sightings AS18379 CSMNAP-AS-AP - CSMNAP-ASN 259 4,704 0 Collector-only (1)
AS Name AS paths IPv4 sightings IPv6 sightings AS24482 SGGS-AS-AP - SG.GS 1 6 0
Raw RDAP Response
{
"rdapConformance": [
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"notices": [
{
"title": "Source",
"description": [
"Objects returned came from source",
"IDNIC"
]
},
{
"title": "Terms and Conditions",
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format.",
"This information has been partially mirrored by APNIC from IDNIC."
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/17910",
"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://idnic.rdap.apnic.net/autnum/17910",
"rel": "inaccuracy-report",
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"type": "text/html"
}
]
}
],
"country": "ID",
"name": "TIGAKOM-AS-ID",
"status": [
"active"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:30:26Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-12-01T09:18:31Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/17910",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/autnum/17910",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"PT. Tigatra Infokom",
"Jakarta"
],
"title": "description"
}
],
"entities": [
{
"roles": [
"technical"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:29:03Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-11-30T05:43:43Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/17910",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/entity/RP526-AP",
"type": "application/rdap+json"
}
],
"handle": "RP526-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
},
{
"roles": [
"abuse"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:29:03Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-11-30T07:11:26Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/17910",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/entity/IRT-TIGAKOM-ID",
"type": "application/rdap+json"
}
],
"handle": "IRT-TIGAKOM-ID",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-TIGAKOM-ID"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "PT. Tigatra Infokom\nPlaza Permata Lt. 10 Jl. MH. Thamrin 57\nJakarta 10350"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
},
{
"roles": [
"administrative"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2019-08-20T06:29:03Z"
},
{
"eventAction": "last changed",
"eventDate": "2016-11-30T05:43:15Z"
}
],
"links": [
{
"value": "https://idnic.rdap.apnic.net/autnum/17910",
"rel": "self",
"href": "https://idnic.rdap.apnic.net/entity/IMSJ1-AP",
"type": "application/rdap+json"
}
],
"handle": "IMSJ1-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
}
],
"handle": "AS17910",
"startAutnum": 17910,
"endAutnum": 17910,
"objectClassName": "autnum",
"port43": "whois.apnic.net"
} Contact details of private individuals are redacted.