Skip to main content

AS395596

INFINIRC-LLC

Infinirc LLC

Registry

Authoritative registration data

AS number
395596
Name
INFINIRC-LLC
Organisation
Infinirc LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS395596
23.145.28.0/24 IPv4 /24 RPKI valid
2602:f573::/40 IPv6 /40 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 AS395596
Address families
STUIX 10,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 AS395596 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS395596 in AS paths

Observed upstreams
Families
AS17408 ABOVE-AS-AP 701 1,022
v6
AS134823 SDCL-AS-AP 209 259
v4 v6
AS150766 CoCoDigit-Ltd 58 76
v4 v6
AS6939 HURRICANE 35 41
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS395596 in AS paths

Observed downstreams
Families
AS207344 Infinirc 244 358
v6
AS216320 Infinirc-LLC 244 358
v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS18041 TWDS-AS-TW 1 4
v4 v6
AS24482 SGGS-AS-AP 1 2
v4 v6
AS38855 STUIX-AS-TW 1 2
v4 v6
AS59105 HOMENOC 1 2
v4 v6
AS207705 JK-NETWORK 1 1
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.