Skip to main content

AS400566

POWERSERG

PowerSerg Data Systems Inc

Registry

Authoritative registration data

AS number
400566
Name
POWERSERG
Organisation
PowerSerg Data Systems Inc
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS400566
199.201.221.0/24 IPv4 /24 not checked
23.134.82.0/24 IPv4 /24 not checked
44.30.97.0/24 IPv4 /24 not checked
2602:fb99::/36 IPv6 /36 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 AS400566
Address families
ARIX: Primary 10,000 Mbps IPv4 · IPv6
FCIX 10,000 Mbps IPv4 · IPv6
FREMIX 10,000 Mbps IPv4 · IPv6
SFMIX 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 AS400566 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS400566 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 305 1,108
v4 v6
AS13335 CLOUDFLARENET 271 367
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS400566 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
AS49544 i3Dnet 1 4
v4
AS36236 NETACTUATE 1 3
v4 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.