Skip to main content

AS209735

LAGRANGE

Lagrange Cloud Technologies Limited

Registry

Authoritative registration data

AS number
209735
Name
LAGRANGE
Organisation
Lagrange Cloud Technologies Limited
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

3

Total announced

5

Announced prefixes

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

Prefixes announced by AS209735
103.146.103.0/24 IPv4 /24 not checked
85.155.100.0/24 IPv4 /24 not checked
2a07:54c2:b00b::/48 IPv6 /48 not checked
2a0f:85c1:80::/48 IPv6 /48 not checked
2a0f:85c1:81::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS209735 in AS paths

Observed upstreams
Families
AS6939 14,385 89,574
v4 v6
AS44355 1,686 4,051
v4 v6
AS207841 41 65
v6
AS8218 4 16
v6
AS39351 4 4
v6

No rows match “”.

Showing of

Observed downstreams

82 networks seen after AS209735 in AS paths

Observed downstreams
Families
AS205710 273 15,260
v6
AS207480 192 11,092
v6
AS206178 193 10,543
v6
AS211980 193 10,192
v6
AS206778 189 9,619
v6
AS206809 164 8,840
v6
AS213124 258 1,415
v6
AS208915 511 1,349
v4 v6
AS47326 382 1,060
v6
AS200279 194 948
v6
AS213302 191 785
v6
AS199632 256 730
v6
AS203202 178 727
v6
AS214781 514 725
v4 v6
AS61087 496 723
v6
AS214909 159 666
v6
AS51939 190 655
v6
AS210880 382 532
v6
AS214428 191 529
v6
AS200104 191 528
v6
AS213434 182 476
v6
AS207118 192 445
v6
AS219251 244 414
v6
AS60431 258 371
v6
AS214690 257 366
v6
AS219214 257 366
v6
AS219351 257 366
v6
AS219424 257 366
v6
AS214533 134 366
v6
AS201182 257 365
v6
AS205398 257 365
v6
AS219039 257 365
v6
AS219066 257 365
v6
AS200332 256 365
v6
AS201423 256 365
v6
AS212811 256 365
v6
AS214882 255 365
v6
AS214206 250 363
v6
AS207738 248 362
v6
AS202615 247 361
v6
AS219158 247 349
v6
AS210066 207 294
v6
AS197378 204 277
v6
AS207940 192 267
v6
AS215212 192 265
v6
AS214394 191 265
v6
AS197649 190 265
v6
AS205474 190 264
v6
AS201075 188 262
v6
AS213906 188 262
v6
AS215521 187 261
v6
AS218985 186 259
v6
AS219272 184 252
v6
AS51019 182 251
v6
AS54148 168 230
v6
AS197346 166 223
v6
AS200840 166 223
v6
AS215936 166 223
v6
AS219525 166 223
v6
AS199037 165 221
v6
AS202751 164 221
v6
AS199874 154 217
v6
AS207972 161 216
v6
AS204261 77 212
v6
AS215022 158 208
v6
AS201674 145 208
v6
AS219458 64 198
v6
AS208051 134 187
v6
AS214989 139 181
v6
AS215475 83 117
v6
AS201666 43 110
v6
AS199890 74 98
v6
AS207907 72 97
v6
AS208487 24 88
v6
AS213543 56 76
v6
AS208301 53 65
v6
AS215134 52 64
v6
AS201212 11 48
v6
AS202902 19 30
v6
AS59426 10 10
v4
AS39592 7 7
v4
AS219034 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 4 11
v4 v6
AS24482 2 9
v6
AS25160 2 3
v6
AS48185 1 3
v6
AS917 2 2
v6
AS3170 2 2
v6
AS31122 2 2
v6
AS31742 2 2
v6
AS34927 2 2
v6
AS35266 2 2
v6
AS39122 2 2
v6
AS48070 2 2
v6
AS50300 2 2
v6
AS36236 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.