Skip to main content

AS216107

FRUMENTUM

Frumentum Media

Registry

Authoritative registration data

AS number
216107
Name
FRUMENTUM
Organisation
Frumentum Media
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

15

Total announced

16

Announced prefixes

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

Prefixes announced by AS216107
185.234.20.0/24 IPv4 /24 not checked
2a0c:e640::/32 IPv6 /32 not checked
2a05:dfc1:9300::/44 IPv6 /44 RPKI valid
2a0e:b107:2880::/46 IPv6 /46 RPKI valid
2a05:dfc1:c53::/48 IPv6 /48 not checked
2a05:dfc1:cb1::/48 IPv6 /48 not checked
2a05:dfc1:cb2::/48 IPv6 /48 not checked
2a05:dfc1:cd3::/48 IPv6 /48 not checked
2a05:dfc1:cec::/48 IPv6 /48 not checked
2a05:dfc1:cff::/48 IPv6 /48 not checked
2a0c:e640::/48 IPv6 /48 not checked
2a0c:e640:d101::/48 IPv6 /48 not checked
2a0c:e640:d201::/48 IPv6 /48 not checked
2a0c:e640:d301::/48 IPv6 /48 not checked
2a0c:e640:d53::/48 IPv6 /48 not checked
2a0c:e640:d54::/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 AS216107
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
F4IX MCI 1,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
HOUIX: Main 1,000 Mbps IPv4 · IPv6
KCIX 1,000 Mbps IPv4 · IPv6
STLIX: Main 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 AS216107 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS216107 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS216107 in AS paths

Observed downstreams
Families
AS197919 NOAHVDAA-AS 148 858
v6
AS216455 STING 39 48
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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