Skip to main content

AS35200

TransitX-Ltd

TransitX Ltd

Registry

Authoritative registration data

AS number
35200
Name
TransitX-Ltd
Organisation
TransitX Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

28

IPv6 prefixes

0

Total announced

28

Announced prefixes

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

Prefixes announced by AS35200
185.113.128.0/23 IPv4 /23 not checked
45.155.100.0/23 IPv4 /23 not checked
96.9.214.0/23 IPv4 /23 not checked
176.123.62.0/24 IPv4 /24 not checked
179.61.181.0/24 IPv4 /24 not checked
181.215.140.0/24 IPv4 /24 not checked
181.215.25.0/24 IPv4 /24 not checked
185.242.156.0/24 IPv4 /24 not checked
185.242.157.0/24 IPv4 /24 not checked
185.242.158.0/24 IPv4 /24 not checked
185.242.159.0/24 IPv4 /24 not checked
185.72.150.0/24 IPv4 /24 not checked
192.31.26.0/24 IPv4 /24 not checked
192.35.198.0/24 IPv4 /24 not checked
193.223.79.0/24 IPv4 /24 not checked
194.169.80.0/24 IPv4 /24 not checked
194.169.81.0/24 IPv4 /24 not checked
82.22.56.0/24 IPv4 /24 not checked
82.22.58.0/24 IPv4 /24 not checked
82.26.120.0/24 IPv4 /24 not checked
82.26.140.0/24 IPv4 /24 not checked
82.38.182.0/24 IPv4 /24 not checked
82.38.33.0/24 IPv4 /24 not checked
82.38.99.0/24 IPv4 /24 not checked
82.39.144.0/24 IPv4 /24 not checked
82.39.153.0/24 IPv4 /24 not checked
82.39.184.0/24 IPv4 /24 not checked
82.39.204.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS35200 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS35200 in AS paths

Observed upstreams
Families
AS9002 4,370 41,085
v4 v6
AS42831 2,372 11,352
v4 v6
AS3257 560 6,788
v4
AS2914 678 6,614
v4 v6
AS1257 52 625
v4 v6
AS39351 16 162
v4
AS286 5 65
v4
AS2856 6 15
v4

No rows match “”.

Showing of

Observed downstreams

44 networks seen after AS35200 in AS paths

Observed downstreams
Families
AS199741 574 18,556
v4 v6
AS42831 73 14,109
v4
AS52025 1,345 4,244
v4 v6
AS64080 72 3,678
v4
AS142594 478 3,362
v4 v6
AS207108 493 2,443
v4 v6
AS202448 496 2,364
v4 v6
AS136787 81 1,852
v4
AS212396 660 1,391
v4
AS7489 89 1,246
v4
AS205072 243 1,127
v4
AS200260 68 1,074
v4
AS58051 484 1,020
v4 v6
AS46261 88 680
v4
AS57672 425 675
v4 v6
AS59676 220 556
v4
AS47625 72 550
v4
AS27176 92 441
v4
AS8669 72 368
v4
AS61272 102 363
v4
AS400345 263 340
v4
AS201999 247 323
v4
AS41745 79 301
v4
AS208711 145 278
v4
AS215322 130 227
v4 v6
AS395092 81 206
v4
AS393960 74 187
v4
AS216307 71 182
v4
AS214271 43 114
v4
AS44955 41 104
v4
AS34412 20 104
v4
AS8902 49 102
v4 v6
AS51692 76 99
v4
AS64245 74 94
v4
AS215419 73 93
v4
AS61978 72 92
v4
AS201323 72 92
v4
AS216382 72 92
v4
AS1004 71 91
v4
AS214347 29 72
v4
AS60079 19 24
v4
AS35280 1 1
v4
AS39120 1 1
v4
AS200240 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS3170 189 939
v4 v6
AS1828 45 571
v4 v6
AS49544 13 192
v4

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.