Skip to main content

AS20686

BISPING

ISP & Citycarrier, Germany

Registry

Authoritative registration data

AS number
20686
Name
BISPING
Organisation
ISP & Citycarrier, Germany
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

2

Total announced

16

Announced prefixes

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

Prefixes announced by AS20686
62.91.0.0/16 IPv4 /16 not checked
212.86.128.0/19 IPv4 /19 not checked
217.30.224.0/20 IPv4 /20 not checked
80.85.0.0/20 IPv4 /20 not checked
193.218.208.0/21 IPv4 /21 not checked
193.218.216.0/22 IPv4 /22 not checked
185.97.242.0/23 IPv4 /23 not checked
193.218.220.0/23 IPv4 /23 not checked
130.193.7.0/24 IPv4 /24 not checked
185.245.22.0/24 IPv4 /24 not checked
193.22.166.0/24 IPv4 /24 not checked
193.22.174.0/24 IPv4 /24 not checked
193.22.29.0/24 IPv4 /24 not checked
194.0.151.0/24 IPv4 /24 not checked
2a03:e880::/29 IPv6 /29 not checked
2001:67c:2b30::/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 AS20686
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 100,000 Mbps IPv4 · IPv6
Equinix Frankfurt: Equinix IX - FR Metro 20,000 Mbps IPv4 · IPv6
N-IX: Peering 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 AS20686 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

39 networks seen before AS20686 in AS paths

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS20686 in AS paths

Observed downstreams
Families
AS205496 336 702
v4
AS44231 GEOBRA-BRANDSTAETTER 268 346
v4
AS205382 215 281
v4
AS56719 24 33
v4
AS44973 RZHAS-AS 6 9
v4

No rows match “”.

Showing of

Uncertain adjacencies

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