Skip to main content

AS200544

swiss-defence-afcso

AS3303 is Swisscom

Registry

Authoritative registration data

AS number
200544
Name
swiss-defence-afcso
Organisation
AS3303 is Swisscom
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS200544
159.22.0.0/16 IPv4 /16 not checked
2a07:ad00::/31 IPv6 /31 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 AS200544 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS200544 in AS paths

Observed upstreams
Families
AS15576 NTS 255 364
v4 v6
AS3303 SWISSCOM 112 143
v6
AS9002 RETN-AS 16 20
v6
AS6939 HURRICANE 17 18
v4
AS8218 NEO-ASN 2 16
v4 v6
AS34019 HIVANE 4 12
v4 v6
AS48362 TKSWF-AS 2 8
v4 v6
AS25091 IP-Max 2 7
v4 v6
AS1764 NEXTLAYER-AS 2 6
v4 v6
AS47147 AS-ANX 2 6
v4 v6
AS5405 INTERDOTLINK 3 5
v4 v6
AS24961 MYLOC-AS 2 4
v4 v6
AS39351 ESAB-AS 2 4
v4 v6
AS34177 CELESTE-AS 2 3
v4 v6
AS34927 iFog-GmbH 2 2
v6
AS1836 GREEN 1 2
v4 v6
AS9009 M247 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200544 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

27 adjacencies that may be an artefact of collector peering

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.