Skip to main content

AS204085

DISPAISY-AS2

DisPaisy Enterprises Projects

Registry

Authoritative registration data

AS number
204085
Name
DISPAISY-AS2
Organisation
DisPaisy Enterprises Projects
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

8

Total announced

8

Announced prefixes

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

Prefixes announced by AS204085
2a06:a002:c450::/44 IPv6 /44 not checked
2a14:67c3:1b0::/44 IPv6 /44 not checked
2a06:9801:3::/48 IPv6 /48 RPKI valid
2a06:a002:4085::/48 IPv6 /48 not checked
2a06:a002:a002::/48 IPv6 /48 RPKI valid
2a06:a002:d323::/48 IPv6 /48 not checked
2a14:67c3:1b2::/48 IPv6 /48 not checked
2a14:7583:e111::/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 AS204085
Address families
FogIXP 10,000 Mbps IPv6
FogIXP Frankfurt 10,000 Mbps IPv4 · IPv6
INTERIX 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 AS204085 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS204085 in AS paths

Observed upstreams
Families
AS215760 DISPAISY-AS 460 1,421
v6
AS6939 HURRICANE 176 721
v6
AS16509 AMAZON-02 253 341
v6
AS209533 BGPTunnel 82 305
v6
AS25091 IP-Max 3 14
v6
AS39351 ESAB-AS 2 10
v6
AS47498 FogIXP 2 5
v6
AS209022 Tschajera-Limited 1 5
v6
AS62000 AS62000 1 3
v6
AS205794 RTTW-AS 1 3
v6
AS401753 BIXCE 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204085 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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