Skip to main content

AS139543

MAHABAL-AS-IN

MAHABAL NET SERVICE PROVIDER PRIVATE LIMITED

Registry

Authoritative registration data

AS number
139543
Name
MAHABAL-AS-IN
Organisation
MAHABAL NET SERVICE PROVIDER PRIVATE LIMITED
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS139543
103.171.188.0/24 IPv4 /24 not checked
103.171.189.0/24 IPv4 /24 not checked
2001:df7:7b80::/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 AS139543
Address families
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 10,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 AS139543 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS139543 in AS paths

Observed upstreams
Families
AS18229 CTRLS-AS-IN 293 522
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS139543 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35280 F5 1 3
v4 v6
AS24482 SGGS-AS-AP 1 2
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.