Skip to main content

AS28875

INNO

ORG-IIG10-RIPE

Registry

Authoritative registration data

AS number
28875
Name
INNO
Organisation
ORG-IIG10-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

6

Total announced

10

Announced prefixes

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

Prefixes announced by AS28875
185.104.16.0/24 IPv4 /24 not checked
185.104.18.0/24 IPv4 /24 not checked
45.15.80.0/24 IPv4 /24 not checked
45.15.82.0/24 IPv4 /24 not checked
2a00:f740::/32 IPv6 /32 not checked
2a0e:2b80::/32 IPv6 /32 not checked
2a00:f740:100::/48 IPv6 /48 not checked
2a0e:2b80:100::/48 IPv6 /48 not checked
2a0e:2b80:202::/48 IPv6 /48 not checked
2a0e:2b80::/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 AS28875
Address families
SwissIX: Peering 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 AS28875 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS28875 in AS paths

Observed upstreams
Families
AS29691 NINE 336 2,706
v4 v6
AS6939 HURRICANE 20 80
v4
AS9002 RETN-AS 8 78
v6
AS12307 RAVANA 9 67
v4 v6
AS34019 HIVANE 4 60
v4 v6
AS48362 TKSWF-AS 2 40
v4 v6
AS1764 NEXTLAYER-AS 2 30
v4 v6
AS47147 AS-ANX 2 26
v4 v6
AS5405 INTERDOTLINK 4 22
v4 v6
AS39351 ESAB-AS 2 20
v4 v6
AS24961 MYLOC-AS 2 14
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS28875 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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