Skip to main content

AS209620

LINSPACE

===== TRANSIT COGENT =====

Registry

Authoritative registration data

AS number
209620
Name
LINSPACE
Organisation
===== TRANSIT COGENT =====
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

5

Total announced

15

Announced prefixes

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

Prefixes announced by AS209620
193.58.88.0/22 IPv4 /22 not checked
194.55.240.0/22 IPv4 /22 not checked
78.31.196.0/22 IPv4 /22 not checked
193.58.89.0/24 IPv4 /24 not checked
193.58.90.0/24 IPv4 /24 not checked
193.58.91.0/24 IPv4 /24 not checked
194.55.240.0/24 IPv4 /24 not checked
194.55.241.0/24 IPv4 /24 not checked
194.55.242.0/24 IPv4 /24 not checked
194.55.243.0/24 IPv4 /24 not checked
2a06:6880::/29 IPv6 /29 not checked
2a0c:94c0::/29 IPv6 /29 not checked
2a0c:cbc0::/29 IPv6 /29 not checked
2a0c:cbc2:1000::/36 IPv6 /36 not checked
2a0c:cbc2:2000::/36 IPv6 /36 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 AS209620
Address families
BCIX: BCIX Peering LAN 30,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 AS209620 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS209620 in AS paths

Observed upstreams
Families
AS58243 384 2,940
v4 v6
AS174 COGENT-174 334 1,813
v4 v6
AS21032 TELTA-AS 168 486
v4 v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS209620 in AS paths

Observed downstreams
Families
AS21032 TELTA-AS 21 23
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS680 DFN 1 15
v4 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.