Skip to main content

AS59280

IDNIC-KAILIGLOBAL-AS-ID

PT. Kaili Global

Registry

Authoritative registration data

AS number
59280
Name
IDNIC-KAILIGLOBAL-AS-ID
Organisation
PT. Kaili Global
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS59280
103.228.24.0/23 IPv4 /23 not checked
103.228.26.0/23 IPv4 /23 not checked
103.228.24.0/24 IPv4 /24 not checked
103.228.25.0/24 IPv4 /24 not checked
103.228.26.0/24 IPv4 /24 not checked
103.228.27.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS59280
Address families
IIX-Jakarta 10,000 Mbps IPv4
OpenIXP / NiCE 10,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS59280 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS59280 in AS paths

Observed upstreams
Families
AS24198 DATAKOMNAP-AS-ID 263 656
v4
AS35280 F5 8 48
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59280 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.