Skip to main content

AS21368

PHOENIX-IT

Phoenix IT SRL

Registry

Authoritative registration data

AS number
21368
Name
PHOENIX-IT
Organisation
Phoenix IT SRL
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS21368
185.109.252.0/23 IPv4 /23 not checked
45.86.138.0/23 IPv4 /23 not checked
185.109.252.0/24 IPv4 /24 not checked
185.109.253.0/24 IPv4 /24 not checked
185.109.255.0/24 IPv4 /24 not checked
45.86.137.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS21368 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS21368 in AS paths

Observed upstreams
Families
AS9050 228 867
v4
AS12302 210 774
v4
AS6939 HURRICANE 36 204
v4
AS14840 ASN14840 2 30
v4
AS20764 RASCOM-AS 5 27
v4
AS22356 7 21
v4
AS6204 2 12
v4
AS15958 1 6
v4
AS263444 1 6
v4
AS21215 1 3
v4
AS12310 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS21368 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 57
v4
AS49544 i3Dnet 1 12
v4
AS212483 level86 1 12
v4
AS3233 ICI-ROTLD 1 6
v4
AS13004 1 6
v4
AS29049 1 6
v4
AS31554 1 6
v4
AS33823 1 6
v4
AS35505 1 6
v4
AS36236 NETACTUATE 1 6
v4
AS44901 1 6
v4
AS56430 CHROOT 1 6
v4
AS198150 1 6
v4
AS39668 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.