Skip to main content

AS205755

Sdnbucks

SDNBUCKS BV

Registry

Authoritative registration data

AS number
205755
Name
Sdnbucks
Organisation
SDNBUCKS BV
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 AS205755
185.207.192.0/24 IPv4 /24 not checked
185.207.193.0/24 IPv4 /24 RPKI valid
185.207.194.0/24 IPv4 /24 not checked
185.207.195.0/24 IPv4 /24 RPKI valid
2a0b:2740::/48 IPv6 /48 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 AS205755
Address families
1-NL FREE 100,000 Mbps IPv4 · IPv6
AMS-IX 1,000 Mbps IPv4 · IPv6
EVIX: Peering LAN 1,000 Mbps IPv4 · IPv6
FogIXP 10,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
LSIX: Main 10,000 Mbps IPv4 · IPv6
NSIX Amsterdam 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 10,000 Mbps IPv4 · IPv6
nine 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 AS205755 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

35 networks seen before AS205755 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS205755 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

71 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 35
v4 v6
AS24482 SGGS-AS-AP 1 33
v4 v6
AS12779 ITGATE 1 20
v4 v6
AS47147 AS-ANX 1 17
v4 v6
AS34019 HIVANE 1 15
v4 v6
AS48185 team_blue 1 15
v4 v6
AS15547 NETPLUS 1 11
v4 v6
AS8529 OMANTEL-AS 1 10
v4 v6
AS14907 WIKIMEDIA 1 10
v4 v6
AS49544 i3Dnet 1 10
v4 v6
AS51184 FONIRA 1 10
v4 v6
AS62167 Tismi 1 10
v4 v6
AS212483 level86 1 10
v4 v6
AS34927 iFog-GmbH 1 9
v4 v6
AS51185 MAINSTREAMING-AS 1 9
v4 v6
AS12859 NL-BIT 1 6
v4 v6
AS559 Switch 1 5
v4 v6
AS680 DFN 1 5
v4 v6
AS1103 SURFNET-NL 1 5
v4 v6
AS1140 SIDN 1 5
v4 v6
AS1828 UNITAS 1 5
v4 v6
AS3212 TELEMACH 1 5
v4 v6
AS3333 RIPE-NCC-AS 1 5
v4 v6
AS3399 OBE-NET 1 5
v4 v6
AS5405 INTERDOTLINK 1 5
v4 v6
AS8298 IPNG 1 5
v4 v6
AS15605 CONNESI 1 5
v4 v6
AS20932 SIG-ST 1 5
v4 v6
AS25160 VORBOSS 1 5
v4 v6
AS25220 GLOBALNOC-AS 1 5
v4 v6
AS29075 IELO 1 5
v4 v6
AS29140 HOSTSERVER-AS 1 5
v4 v6
AS34177 CELESTE-AS 1 5
v4 v6
AS35280 F5 1 5
v4 v6
AS36236 NETACTUATE 1 5
v4 v6
AS39122 BLACKNIGHT-AS 1 5
v4 v6
AS41327 FIBERTELECOM-AS 1 5
v4 v6
AS42541 FIBERBY 1 5
v4 v6
AS48919 UA-CITY-AS 1 5
v4 v6
AS49434 FBWNETWORKS 1 5
v4 v6
AS50300 CUSTDC 1 5
v4 v6
AS50763 MCKAYCOM 1 5
v4 v6
AS56987 AS-ABACLOUDA 1 5
v4 v6
AS58299 OPENFACTORY-AS 1 5
v4 v6
AS60326 DEADBEEF-AS 1 5
v4 v6
AS64475 FREIFUNK-FRANKFURT 1 5
v4 v6
AS199938 NETZWERGE 1 5
v4 v6
AS204092 GRIFON 1 5
v4 v6
AS205112 PHILUNET 1 5
v4 v6
AS209823 ENKI-AS 1 5
v4 v6
AS212635 AS212635 1 5
v4 v6
AS271253 ASN271253 1 5
v4 v6
AS2027 MilkyWan 1 4
v4
AS13237 LAMBDANET-AS 1 4
v4
AS14630 INVESCO 1 4
v4
AS16347 INHERENT 1 4
v4
AS35600 ASN-VEDEGE 1 4
v4
AS37721 ORG-VTS1-AFRINIC 1 4
v4
AS44097 AUTONOMOUS-CLOSET 1 4
v4
AS49134 AS_10VPN 1 4
v4
AS49605 DTS-AS 1 4
v4
AS198150 SIACOM-AS 1 4
v4
AS202365 Chronos 1 4
v4
AS263152 ASN263152 1 4
v4
AS28917 Fiord-AS 1 2
v6
AS17639 CONVERGE-AS 1 1
v6
AS45489 SLT-GLOBAL 1 1
v6
AS50673 Serverius-as 1 1
v6
AS51088 A2B 1 1
v6
AS51873 AS-ARCADE 1 1
v6
AS213241 TECHIT 1 1
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.