Skip to main content

AS210233

Pixinko

Pixinko SARL

Registry

Authoritative registration data

AS number
210233
Name
Pixinko
Organisation
Pixinko SARL
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

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

Prefixes announced by AS210233
2a0c:b641:870::/44 IPv6 /44 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 AS210233
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX NETHERLANDS: Peering LAN 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS210233 in AS paths

Observed upstreams
Families
AS24961 399 526
v6
AS25091 IP-Max 12 69
v6
AS34927 iFog-GmbH 10 33
v6
AS8298 IPNG 9 32
v6
AS34549 MEER-AS 4 18
v6
AS401753 4 12
v6
AS48646 3 11
v6

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS210233 in AS paths

Observed downstreams
Families
AS219511 195 467
v6
AS211907 64 86
v6
AS200202 24 28
v6
AS212625 CLEMENTD 6 7
v6

No rows match “”.

Showing of

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS3214 XTOM 5 31
v6
AS56662 4 12
v6
AS199854 4 12
v6
AS34872 Servperso_Systems 3 11
v6
AS41666 3 11
v6
AS210937 Showfom 3 11
v6
AS42541 2 9
v6
AS51185 MAINSTREAMING-AS 2 9
v6
AS209823 2 9
v6
AS213151 2 9
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.