Skip to main content

AS208549

PORTWAKE

Christian Ehrig

Registry

Authoritative registration data

AS number
208549
Name
PORTWAKE
Organisation
Christian Ehrig
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS208549
80.64.220.0/24 IPv4 /24 RPKI valid
80.64.221.0/24 IPv4 /24 RPKI valid
80.64.222.0/24 IPv4 /24 RPKI valid
80.64.223.0/24 IPv4 /24 RPKI valid
2a0d:1cc0::/29 IPv6 /29 RPKI valid

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 AS208549
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: 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 AS208549 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS208549 in AS paths

Observed upstreams
Families
AS34872 Servperso_Systems 399 1,459
v4 v6
AS6939 HURRICANE 22 100
v4
AS208210 Servperso_Systems 8 51
v4 v6
AS25091 IP-Max 5 44
v4 v6
AS14840 ASN14840 2 20
v4
AS401753 BIXCE 1 5
v4 v6
AS34927 iFog-GmbH 2 4
v4 v6
AS263444 ASN263444 1 4
v4
AS31500 GNM-AS 1 1
v4
AS48646 STEFAN6 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS208549 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 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.