Skip to main content

AS216309

INVISIONTECH-GROUP-SRL

InvisionTech Group S.r.l.

Registry

Authoritative registration data

AS number
216309
Name
INVISIONTECH-GROUP-SRL
Organisation
InvisionTech Group S.r.l.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

4

Total announced

5

Announced prefixes

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

Prefixes announced by AS216309
94.249.231.0/24 IPv4 /24 not checked
2a0d:b287:dd00::/40 IPv6 /40 RPKI valid
2a14:7584:4100::/40 IPv6 /40 RPKI valid
2a14:7584:4100::/48 IPv6 /48 RPKI valid
2a14:7584:41ee::/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 AS216309
Address families
MINAP Milan: MINAP 100,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 AS216309 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS216309 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 988 3,726
v4 v6
AS41720 NAVIGABENE 462 690
v4 v6
AS198064 ZEROPACKETS-LTD 137 174
v4
AS14840 ASN14840 5 17
v4
AS24961 MYLOC-AS 8 12
v4 v6
AS9009 M247 3 3
v4
AS22356 ASN22356 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

24 networks seen after AS216309 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

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