Skip to main content

AS200303

LUMASERV

LUMASERV GmbH

Registry

Authoritative registration data

AS number
200303
Name
LUMASERV
Organisation
LUMASERV GmbH
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

14

Total announced

30

Announced prefixes

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

Prefixes announced by AS200303
45.95.52.0/22 IPv4 /22 not checked
185.244.164.0/23 IPv4 /23 not checked
185.244.166.0/23 IPv4 /23 not checked
45.132.124.0/23 IPv4 /23 not checked
45.132.126.0/23 IPv4 /23 not checked
185.244.164.0/24 IPv4 /24 not checked
185.244.166.0/24 IPv4 /24 not checked
185.244.167.0/24 IPv4 /24 not checked
185.245.60.0/24 IPv4 /24 not checked
45.132.124.0/24 IPv4 /24 not checked
45.132.125.0/24 IPv4 /24 not checked
45.132.126.0/24 IPv4 /24 not checked
45.132.127.0/24 IPv4 /24 not checked
45.95.52.0/24 IPv4 /24 not checked
45.95.54.0/24 IPv4 /24 not checked
91.246.47.0/24 IPv4 /24 not checked
2a0d:3580::/32 IPv6 /32 not checked
2a0d:3585::/32 IPv6 /32 not checked
2a0d:3580:12db::/48 IPv6 /48 not checked
2a0d:3580:12dc::/48 IPv6 /48 not checked
2a0d:3580:12dd::/48 IPv6 /48 not checked
2a0d:3580:12de::/48 IPv6 /48 not checked
2a0d:3580:12df::/48 IPv6 /48 not checked
2a0d:3580:12ea::/48 IPv6 /48 not checked
2a0d:3580:12eb::/48 IPv6 /48 not checked
2a0d:3580:12ec::/48 IPv6 /48 not checked
2a0d:3580:12ed::/48 IPv6 /48 not checked
2a0d:3580:12ee::/48 IPv6 /48 not checked
2a0d:3580:12ef::/48 IPv6 /48 not checked
2a0d:3584:1111::/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 AS200303
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 1,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 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 AS200303 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS200303 in AS paths

Observed upstreams
Families
AS30823 AUROLOGIC 619 4,214
v4 v6
AS6939 HURRICANE 229 3,630
v6
AS48314 IP-PROJECTS 256 1,460
v4 v6
AS6204 319 1,221
v4 v6
AS24940 HETZNER-AS 271 831
v4 v6
AS29691 NINE 274 368
v4
AS20473 226 331
v4 v6
AS25091 IP-Max 3 66
v6
AS5405 2 22
v6
AS8298 IPNG 2 22
v6
AS34927 iFog-GmbH 2 22
v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS200303 in AS paths

Observed downstreams
Families
AS203437 268 1,357
v4
AS210633 272 358
v6
AS42335 50 60
v4

No rows match “”.

Showing of

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 99
v6
AS35710 WEBERCLOUD 1 22
v6
AS3214 XTOM 1 11
v6
AS34549 MEER-AS 1 11
v6
AS41327 FIBERTELECOM-AS 1 11
v6
AS45489 SLT-GLOBAL 1 11
v6
AS50629 LWLCOM 1 11
v6
AS56662 1 11
v6
AS58057 SECUREBIT 1 11
v6
AS58299 OPENFACTORY-AS 1 11
v6
AS64475 1 11
v6
AS199938 1 11
v6
AS205112 PHILUNET 1 11
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.