Skip to main content

AS47875

PROVINCIA-DI-PADOVA-AS

Provincia di Padova

Registry

Authoritative registration data

AS number
47875
Name
PROVINCIA-DI-PADOVA-AS
Organisation
Provincia di Padova
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS47875
94.124.32.0/22 IPv4 /22 not checked
94.124.36.0/22 IPv4 /22 not checked
94.124.35.0/24 IPv4 /24 not checked
94.124.36.0/24 IPv4 /24 not checked
94.124.37.0/24 IPv4 /24 not checked
94.124.38.0/24 IPv4 /24 not checked
94.124.39.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

Internet Exchange memberships listed for AS47875
Address families
VSIX: Primary 2,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 AS47875 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS47875 in AS paths

Observed upstreams
Families
AS12874 769 2,163
v4
AS3269 ASN-IBSNAZ 132 217
v4
AS24961 4 4
v4
AS1267 2 2
v4
AS2593 2 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS47875 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS12637 2 2
v4
AS50877 2 2
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.