Skip to main content

AS44219

ICCOM-AS

Iccom S.r.l.

Registry

Authoritative registration data

AS number
44219
Name
ICCOM-AS
Organisation
Iccom S.r.l.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS44219
178.249.220.0/22 IPv4 /22 not checked
94.247.188.0/22 IPv4 /22 RPKI valid
178.249.216.0/23 IPv4 /23 not checked
178.249.218.0/23 IPv4 /23 RPKI valid
194.39.144.0/23 IPv4 /23 not checked
194.39.146.0/23 IPv4 /23 not checked
94.247.184.0/23 IPv4 /23 not checked
94.247.186.0/23 IPv4 /23 not checked
2a00:1cb0::/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 AS44219
Address families
France-IX Paris 1,000 Mbps IPv4
TOP-IX: Public Peering VLAN 10,000 Mbps IPv4

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 AS44219 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS44219 in AS paths

Observed upstreams
Families
AS12779 ITGATE 331 2,488
v4 v6
AS6939 HURRICANE 16 136
v4
AS8218 NEO-ASN 2 64
v4
AS25091 IP-Max 3 40
v4
AS34019 HIVANE 2 32
v4
AS3303 SWISSCOM 3 24
v4
AS6057 6057 2 16
v4
AS35280 F5 2 16
v4
AS39351 ESAB-AS 2 16
v4
AS4455 BSO 1 8
v4
AS6758 AS6758 1 8
v4
AS7713 telkomnet-as-ap 1 8
v4
AS20766 GITOYEN-MAIN-AS 1 8
v4
AS60171 AFRIX-AS 1 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS44219 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.