Skip to main content

AS29513

FOLIATEAM

FOLIATEAM GROUP

Registry

Authoritative registration data

AS number
29513
Name
FOLIATEAM
Organisation
FOLIATEAM GROUP
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS29513
217.64.48.0/20 IPv4 /20 RPKI valid
89.251.48.0/20 IPv4 /20 not checked
146.66.144.0/21 IPv4 /21 RPKI valid
37.60.184.0/21 IPv4 /21 RPKI valid
46.31.208.0/21 IPv4 /21 not checked
80.64.224.0/21 IPv4 /21 not checked
194.180.228.0/22 IPv4 /22 not checked
146.66.149.0/24 IPv4 /24 RPKI valid
193.105.225.0/24 IPv4 /24 not checked
2a06:15c0::/29 IPv6 /29 RPKI valid
2a01:1c0::/32 IPv6 /32 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 AS29513
Address families
France-IX Paris 10,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 AS29513 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS29513 in AS paths

Observed upstreams
Families
AS8218 NEO-ASN 293 2,614
v4 v6
AS3215 AS3215 259 457
v4
AS6939 HURRICANE 54 219
v4 v6
AS34019 HIVANE 3 38
v4 v6
AS9002 RETN-AS 6 20
v6
AS6057 6057 2 18
v4 v6
AS39351 ESAB-AS 2 18
v4 v6
AS34177 CELESTE-AS 2 16
v4 v6
AS35280 F5 2 11
v4 v6
AS6758 AS6758 1 9
v4 v6
AS60171 AFRIX-AS 1 9
v4 v6
AS4455 BSO 1 8
v4 v6
AS7713 telkomnet-as-ap 1 7
v4
AS20766 GITOYEN-MAIN-AS 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS29513 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

27 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.