Skip to main content

AS214815

AMFORC-AS

ORG-ISA1-RIPE

Registry

Authoritative registration data

AS number
214815
Name
AMFORC-AS
Organisation
ORG-ISA1-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS214815
147.189.163.0/24 IPv4 /24 not checked
91.90.166.0/24 IPv4 /24 not checked
2001:67c:328::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS214815 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS214815 in AS paths

Observed upstreams
Families
AS13030 INIT7 103 300
v4 v6
AS61423 JMP-AS 100 279
v4 v6
AS6939 HURRICANE 66 104
v4 v6
AS34019 HIVANE 4 15
v4 v6
AS9002 RETN-AS 9 12
v6
AS48362 TKSWF-AS 2 12
v4 v6
AS47147 AS-ANX 2 9
v4 v6
AS1764 NEXTLAYER-AS 2 7
v4 v6
AS24961 MYLOC-AS 2 6
v4 v6
AS34177 CELESTE-AS 2 5
v4 v6
AS39351 ESAB-AS 1 3
v4 v6
AS9009 M247 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS214815 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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