Skip to main content

AS47116

INTELLIHOME-AS

UPSTREAMS:

Registry

Authoritative registration data

AS number
47116
Name
INTELLIHOME-AS
Organisation
UPSTREAMS:
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS47116
31.223.232.0/21 IPv4 /21 not checked
93.189.112.0/21 IPv4 /21 not checked
185.91.184.0/22 IPv4 /22 not checked
37.143.76.0/22 IPv4 /22 not checked
2a00:10b8::/32 IPv6 /32 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 AS47116
Address families
BIX 20,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 AS47116 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS47116 in AS paths

Observed upstreams
Families
AS62214 RACKFOREST-AS 1,151 3,548
v4 v6
AS6939 HURRICANE 290 574
v4 v6
AS33891 CORE-BACKBONE 24 66
v4 v6
AS15576 NTS 14 58
v4 v6
AS47692 NESSUS 8 52
v4 v6
AS6663 TTI-NET 4 13
v4 v6
AS15958 CETIN_doo_AS 4 10
v4
AS21215 UGNI 4 10
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS47116 in AS paths

Observed downstreams
Families
AS199235 MIKROHALO-HU-AS 415 1,345
v4 v6
AS207693 TELEKABEL-AS 416 1,012
v4 v6
AS200864 cogitnetas1 260 333
v4

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 4 26
v4 v6
AS40994 Alwyzon 4 13
v4 v6

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.