Skip to main content

AS49690

SGT-FR

-----------------------------------------------------

Registry

Authoritative registration data

AS number
49690
Name
SGT-FR
Organisation
-----------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS49690
159.151.0.0/18 IPv4 /18 RPKI valid
192.109.140.0/24 IPv4 /24 not checked
192.109.141.0/24 IPv4 /24 not checked
2a07:8140::/36 IPv6 /36 RPKI valid

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 AS49690
Address families
Equinix Paris: Equinix IX - PA Metro 10,000 Mbps IPv4 · IPv6
France-IX Paris 100,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 AS49690 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

19 networks seen before AS49690 in AS paths

Observed upstreams
Families
AS6461 ZAYO-6461 120 542
v4 v6
AS3356 LEVEL3 150 468
v4 v6
AS6939 HURRICANE 17 51
v4
AS5405 INTERDOTLINK 6 26
v4 v6
AS12779 ITGATE 2 19
v4 v6
AS9002 RETN-AS 12 18
v6
AS25091 IP-Max 3 17
v4 v6
AS34019 HIVANE 3 17
v4 v6
AS6057 6057 2 8
v4 v6
AS39351 ESAB-AS 2 8
v4 v6
AS3303 SWISSCOM 2 7
v4 v6
AS34927 iFog-GmbH 2 7
v4 v6
AS20562 OPEN-PEERING-AS 2 5
v4 v6
AS35280 F5 2 5
v4 v6
AS4455 BSO 1 4
v4 v6
AS6758 AS6758 1 4
v4 v6
AS60171 AFRIX-AS 1 4
v4 v6
AS20766 GITOYEN-MAIN-AS 1 3
v4
AS35661 VIRTUASYS-EU 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49690 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

24 adjacencies that may be an artefact of collector peering

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.