Skip to main content

AS141842

CODEBIT-AS-IN

Codebits Technologies LLP

Registry

Authoritative registration data

AS number
141842
Name
CODEBIT-AS-IN
Organisation
Codebits Technologies LLP
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS141842
103.168.75.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 AS141842
Address families
AMS-IX Mumbai 1,000 Mbps IPv4 · IPv6
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 10,000 Mbps IPv4
Extreme IX Mumbai: Extreme IX 100,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 AS141842 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS141842 in AS paths

Observed upstreams
Families
AS133296 WEBWERKS-AS-IN 248 316
v4
AS8966 Etisalat-AS 9 11
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS141842 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

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