Skip to main content

AS198128

ASN-CONNECTING

Connecting Project s.r.l.

Registry

Authoritative registration data

AS number
198128
Name
ASN-CONNECTING
Organisation
Connecting Project s.r.l.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

0

Total announced

10

Announced prefixes

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

Prefixes announced by AS198128
128.127.56.0/21 IPv4 /21 not checked
167.148.36.0/22 IPv4 /22 RPKI valid
185.103.52.0/22 IPv4 /22 not checked
193.207.32.0/22 IPv4 /22 RPKI valid
193.207.36.0/22 IPv4 /22 RPKI valid
193.207.40.0/22 IPv4 /22 not checked
193.207.44.0/22 IPv4 /22 not checked
82.109.200.0/22 IPv4 /22 not checked
82.38.84.0/22 IPv4 /22 RPKI valid
82.24.201.0/24 IPv4 /24 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 AS198128
Address families
MIX-IT 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 AS198128 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS198128 in AS paths

Observed upstreams
Families
AS39120 CONVERGENZE-AS 137 1,626
v4
AS6762 SEABONE-NET 78 813
v4
AS6939 HURRICANE 18 182
v4
AS8218 NEO-ASN 4 90
v4
AS4455 BSO 2 30
v4
AS5405 INTERDOTLINK 2 20
v4
AS24961 MYLOC-AS 2 12
v4
AS29075 IELO 2 12
v4
AS6204 ZET-NET 1 10
v4
AS31543 MYNET-AS 1 10
v4
AS60171 AFRIX-AS 1 10
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS198128 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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