Skip to main content

AS141519

YUVACOM-AS-IN

Yuvaa Communications Private Limited

Registry

Authoritative registration data

AS number
141519
Name
YUVACOM-AS-IN
Organisation
Yuvaa Communications Private Limited
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS141519
103.162.164.0/24 IPv4 /24 not checked
2407:19c0::/36 IPv6 /36 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 AS141519
Address families
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 1,000 Mbps IPv4 · IPv6
Extreme IX Bangalore 1,000 Mbps IPv4 · IPv6
Extreme IX Mumbai: Extreme IX 10,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 AS141519 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS141519 in AS paths

Observed upstreams
Families
AS134674 TATAPLAYBROADBAND-AS-AP 706 2,339
v4 v6
AS9583 SIFY-AS-IN 2 4
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS141519 in AS paths

Observed downstreams
Families
AS135220 353 1,677
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35280 F5 2 7
v4 v6

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.