Skip to main content

AS154950

IRINN-CRIPL-AS-IN

CRAPPLET INFOTECH PRIVATE LIMITED

Registry

Authoritative registration data

AS number
154950
Name
IRINN-CRIPL-AS-IN
Organisation
CRAPPLET INFOTECH PRIVATE LIMITED
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 AS154950
163.52.252.0/23 IPv4 /23 not checked
103.228.73.0/24 IPv4 /24 not checked
163.5.191.0/24 IPv4 /24 not checked
77.107.95.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 AS154950
Address families
EVIX: Peering LAN 1,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 AS154950 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS154950 in AS paths

Observed upstreams
Families
AS55470 CYFUTURE-AS-IN 385 759
v4
AS11967 HOP179 280 613
v4
AS37989 DCS1PTELTD-AS-AP 13 39
v4
AS212508 LOWHOSTING-AS 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS154950 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49134 AS_10VPN 1 4
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.