Skip to main content

AS202414

CITRA

Communications and Information Technology Regulatory Authority

Registry

Authoritative registration data

AS number
202414
Name
CITRA
Organisation
Communications and Information Technology Regulatory Authority
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

4

Total announced

6

Announced prefixes

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

Prefixes announced by AS202414
194.54.136.0/23 IPv4 /23 not checked
194.54.138.0/23 IPv4 /23 not checked
2a0c:c9c0::/29 IPv6 /29 not checked
2a0c:c9c0::/48 IPv6 /48 not checked
2a0c:c9c2:1::/48 IPv6 /48 not checked
2a0c:c9c2:aa::/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 AS202414
Address families
ix.kw: IXP-LAN 40,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 AS202414 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS202414 in AS paths

Observed upstreams
Families
AS15412 FLAG-AS 424 1,809
v4 v6
AS21050 260 333
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS202414 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
AS8529 OMANTEL-AS 1 8
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.