Skip to main content

AS17483

CITYON-AS-AP

CityOnline Services Ltd

Registry

Authoritative registration data

AS number
17483
Name
CITYON-AS-AP
Organisation
CityOnline Services Ltd
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

41

IPv6 prefixes

11

Total announced

52

Announced prefixes

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

Prefixes announced by AS17483
103.168.177.0/24 IPv4 /24 not checked
103.5.16.0/24 IPv4 /24 not checked
103.5.18.0/24 IPv4 /24 not checked
202.62.64.0/24 IPv4 /24 not checked
202.62.65.0/24 IPv4 /24 not checked
202.62.66.0/24 IPv4 /24 not checked
202.62.67.0/24 IPv4 /24 not checked
202.62.68.0/24 IPv4 /24 not checked
202.62.69.0/24 IPv4 /24 not checked
202.62.70.0/24 IPv4 /24 not checked
202.62.71.0/24 IPv4 /24 not checked
202.62.72.0/24 IPv4 /24 not checked
202.62.73.0/24 IPv4 /24 not checked
202.62.74.0/24 IPv4 /24 not checked
202.62.75.0/24 IPv4 /24 not checked
202.62.76.0/24 IPv4 /24 not checked
202.62.77.0/24 IPv4 /24 not checked
202.62.78.0/24 IPv4 /24 not checked
202.62.79.0/24 IPv4 /24 not checked
202.62.80.0/24 IPv4 /24 not checked
202.62.81.0/24 IPv4 /24 not checked
202.62.82.0/24 IPv4 /24 not checked
202.62.83.0/24 IPv4 /24 not checked
202.62.84.0/24 IPv4 /24 not checked
202.62.85.0/24 IPv4 /24 not checked
202.62.86.0/24 IPv4 /24 not checked
202.62.87.0/24 IPv4 /24 not checked
202.62.88.0/24 IPv4 /24 not checked
202.62.89.0/24 IPv4 /24 not checked
202.62.90.0/24 IPv4 /24 not checked
202.62.91.0/24 IPv4 /24 not checked
202.62.92.0/24 IPv4 /24 not checked
202.62.93.0/24 IPv4 /24 not checked
202.62.94.0/24 IPv4 /24 not checked
202.62.95.0/24 IPv4 /24 not checked
45.123.24.0/24 IPv4 /24 not checked
45.123.25.0/24 IPv4 /24 not checked
45.123.26.0/24 IPv4 /24 not checked
45.123.27.0/24 IPv4 /24 not checked
49.156.155.0/24 IPv4 /24 not checked
49.156.159.0/24 IPv4 /24 not checked
2404:f100:100::/40 IPv6 /40 not checked
2404:f100:200::/40 IPv6 /40 not checked
2404:f100:300::/40 IPv6 /40 not checked
2404:f100:400::/40 IPv6 /40 not checked
2404:f100:500::/40 IPv6 /40 not checked
2404:f100::/40 IPv6 /40 not checked
2404:f100:e000::/40 IPv6 /40 not checked
2404:f100:e100::/40 IPv6 /40 not checked
2404:f100:e200::/40 IPv6 /40 not checked
2404:f100:f000::/40 IPv6 /40 not checked
2001:df3:1d40::/48 IPv6 /48 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 AS17483
Address families
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 10,000 Mbps IPv4
Extreme IX Hyderabad: Extreme IX LAN 10,000 Mbps IPv4
Extreme IX Mumbai: Extreme IX 10,000 Mbps IPv4
NIXI Hyderabad 10,000 Mbps IPv4 · IPv6
NIXI Mumbai 11,000 Mbps IPv4 · IPv6

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 AS17483 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS17483 in AS paths

Observed upstreams
Families
AS45820 TTSL-MEISISP 782 9,846
v4
AS9583 SIFY-AS-IN 597 7,703
v4 v6
AS4755 TATACOMM-AS 262 335
v4
AS17762 1 7
v4
AS134014 1 1
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS17483 in AS paths

Observed downstreams
Families
AS138755 263 668
v4
AS149593 265 342
v4
AS134334 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS142289 1 68
v4 v6
AS24482 SGGS-AS-AP 1 34
v4 v6
AS36236 NETACTUATE 1 34
v4 v6
AS45489 SLT-GLOBAL 1 34
v4 v6
AS35280 F5 3 21
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.