Skip to main content

AS138317

GAURAVCO-AS

Gaurav Communication Pvt. Ltd.

Registry

Authoritative registration data

AS number
138317
Name
GAURAVCO-AS
Organisation
Gaurav Communication Pvt. Ltd.
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS138317
103.132.196.0/24 IPv4 /24 not checked
103.132.197.0/24 IPv4 /24 not checked
103.132.198.0/24 IPv4 /24 not checked
103.132.199.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 AS138317
Address families
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 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 AS138317 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS138317 in AS paths

Observed upstreams
Families
AS58678 450 1,827
v4
AS150605 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS138317 in AS paths

Observed downstreams
Families
AS150605 193 487
v4
AS137109 1 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS142289 2 16
v4
AS24482 SGGS-AS-AP 2 8
v4
AS36236 NETACTUATE 2 8
v4
AS45489 SLT-GLOBAL 2 8
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.