Skip to main content

AS200676

Svens-Jansons

Svens Jansons

Registry

Authoritative registration data

AS number
200676
Name
Svens-Jansons
Organisation
Svens Jansons
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

7

Total announced

7

Announced prefixes

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

Prefixes announced by AS200676
2a06:a003:1111::/48 IPv6 /48 RPKI valid
2a06:a003::/48 IPv6 /48 not checked
2a06:a003:b00b::/48 IPv6 /48 not checked
2a0a:6040:b1f2::/48 IPv6 /48 not checked
2a0a:6040:b1f3::/48 IPv6 /48 not checked
2a0a:6040:b1f4::/48 IPv6 /48 not checked
2a0a:6040:b1f5::/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 AS200676
Address families
4b42 Internet Exchange Point: Switzerland 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 AS200676 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS200676 in AS paths

Observed upstreams
Families
AS34927 iFog-GmbH 259 1,064
v6
AS56630 MELBICOM-EU-AS 289 799
v6
AS8849 MELBICOM-EU-AS 195 583
v6
AS47498 FogIXP 6 9
v6
AS205794 RTTW-AS 1 4
v6
AS209022 Tschajera-Limited 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS200676 in AS paths

Observed downstreams
Families
AS201504 SAULITIS-AS 241 332
v6

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8298 IPNG 1 4
v6
AS39351 ESAB-AS 1 4
v6
AS41666 PYRO-AS 1 4
v6
AS58299 OPENFACTORY-AS 1 4
v6
AS60326 DEADBEEF-AS 1 4
v6
AS209823 ENKI-AS 1 4
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.