Skip to main content

AS13250

BACKBONE-CH

TRANSIT

Registry

Authoritative registration data

AS number
13250
Name
BACKBONE-CH
Organisation
TRANSIT
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS13250
212.117.192.0/19 IPv4 /19 not checked
212.117.204.0/24 IPv4 /24 not checked
2a03:380::/32 IPv6 /32 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 AS13250
Address families
SwissIX: Peering 1,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 AS13250 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS13250 in AS paths

Observed upstreams
Families
AS34309 LINK11 257 335
v4
AS1299 TWELVE99 88 164
v4 v6
AS174 COGENT-174 68 114
v4 v6
AS6939 HURRICANE 60 91
v4 v6
AS3257 GTT-BACKBONE 41 67
v4 v6
AS3491 PCCWG-APAC-HK 27 30
v4
AS6730 SUNRISE 14 22
v4 v6
AS9002 RETN-AS 9 13
v6
AS34019 HIVANE 4 12
v4 v6
AS13030 INIT7 3 10
v4 v6
AS48362 TKSWF-AS 2 7
v4 v6
AS5405 INTERDOTLINK 3 6
v4 v6
AS47147 AS-ANX 2 6
v4 v6
AS58299 OPENFACTORY-AS 3 4
v4 v6
AS1764 NEXTLAYER-AS 2 4
v4 v6
AS24961 MYLOC-AS 2 4
v4 v6
AS33891 CORE-BACKBONE 2 4
v4 v6
AS39351 ESAB-AS 2 4
v4 v6
AS286 KPN 1 2
v4 v6
AS1836 GREEN 1 2
v4 v6
AS4601 DNET 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS13250 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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