Skip to main content

AS202693

mosel

=== Upstreams ===

Registry

Authoritative registration data

AS number
202693
Name
mosel
Organisation
=== Upstreams ===
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

8

Total announced

9

Announced prefixes

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

Prefixes announced by AS202693
80.75.220.0/24 IPv4 /24 not checked
2a06:c640::/32 IPv6 /32 not checked
2a06:c641::/32 IPv6 /32 not checked
2a06:c642::/32 IPv6 /32 not checked
2a06:c643::/32 IPv6 /32 not checked
2a06:c644::/32 IPv6 /32 not checked
2a06:c645::/32 IPv6 /32 not checked
2a06:c646::/32 IPv6 /32 not checked
2a06:c647::/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 AS202693
Address families
BGP.Exchange - Frankfurt 1,000 Mbps IPv6
FogIXP 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 AS202693 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS202693 in AS paths

Observed upstreams
Families
AS34927 iFog-GmbH 286 2,359
v4 v6
AS20473 114 809
v4 v6
AS35661 14 108
v4 v6
AS14840 ASN14840 2 5
v4
AS39351 ESAB-AS 2 2
v4
AS50869 2 2
v4
AS47498 FogIXP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS202693 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS212483 level86 1 2
v4
AS8298 1 1
v4
AS29049 1 1
v4
AS41666 1 1
v4
AS58299 OPENFACTORY-AS 1 1
v4
AS198150 1 1
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.