Skip to main content

AS42764

ORG-AS304-RIPE

Arpitel s.r.l.

Registry

Authoritative registration data

AS number
42764
Name
ORG-AS304-RIPE
Organisation
Arpitel s.r.l.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS42764
149.7.210.0/23 IPv4 /23 not checked
154.63.172.0/23 IPv4 /23 not checked
185.43.16.0/23 IPv4 /23 not checked
149.7.213.0/24 IPv4 /24 not checked
185.43.18.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS42764 in AS paths

Observed upstreams
Families
AS12874 FASTWEB 852 1,906
v4
AS174 COGENT-174 509 782
v4
AS28716 RETELIT-AS 40 49
v4
AS12779 ITGATE 2 5
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS42764 in AS paths

Observed downstreams
Families
AS62054 263 684
v4
AS60017 259 344
v4

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS12637 SEEWEB 1 1
v4
AS15605 CONNESI 1 1
v4
AS20912 1 1
v4
AS51185 MAINSTREAMING-AS 1 1
v4
AS57111 1 1
v4

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.