Summary

  • ARIN records AS393598 under the name AFFINITYCU and links it to registrant handle ACU-67, whose organisation name is Affinity Credit Union 2013. That is a public coordination record, not a live-network test.
  • RIPEstat reported the ASN as announced at its 6 August 2026 observation time and listed three IPv4 /24 prefixes. Those observations are useful evidence of routing activity within a stated window, but they do not establish authorization, universal reachability, service health or security.

The registry gives the network a durable identity

The Border Gateway Protocol, usually shortened to BGP, is how independently operated networks tell one another which internet addresses they can reach. An ASN is the unique number attached to one of those routing domains. It helps other operators distinguish one network’s announcements and routing policy from another’s.

The ARIN RDAP record for AS393598 covers exactly one number: both its starting and ending ASN are 393598. The object handle is AS393598, its name is AFFINITYCU, and it points to ACU-67 as the registrant. The record shows registration and last-change events dated 29 August 2014.

ARIN’s separate entity record for ACU-67 names the organisation Affinity Credit Union 2013 and records Saskatoon, Saskatchewan, Canada as its locality. It also identifies administrative, technical, network-operations and abuse coordination roles through related handles.

This is valuable infrastructure information even though it is administrative. A network operator investigating an unexpected route needs to know which public registry object is associated with the ASN and where a coordination request should begin. A stable number and recorded organisation reduce ambiguity when several companies have similar names or when an incident crosses organisational boundaries.

The record’s limits are just as important. A registry can say who is listed for a number without saying whether that number is announcing routes now. Registration and last-change dates do not prove uninterrupted control or operation since 2014. Contact roles do not measure response time. Nothing in these two responses demonstrates reachability, traffic, redundancy, cybersecurity or the condition of a member service.

RIPEstat adds a time-bounded routing observation

RIPEstat’s AS overview for AS393598 answers a different question. Its response identifies resource 393598, reports the holder label AFFINITYCU - Affinity Credit Union 2013, and marks the ASN as announced for a query timestamp of 6 August 2026 at 16:00 UTC. It also places the number within the 393216–394239 block described as assigned by ARIN.

The announced-prefixes response lists three IPv4 routes in its returned window:

  • 192.64.156.0/24
  • 45.41.210.0/24
  • 45.41.211.0/24

Each returned timeline begins on 23 July and ends on 6 August 2026 at 16:00 UTC. A /24 is a block of 256 IPv4 addresses. In this context, the rows indicate that the measurement product associated those three address blocks with announcements from AS393598 during the stated interval.

For a question about observed routing, this dated evidence is more relevant than an administrative registry date. It is closer to what the routing system was doing. That does not make the response a universal or permanent verdict. Route observations depend on collection points, timing and the paths visible to them. A route seen by a measurement service may not be preferred or reachable from every network, and a route that is not seen from one view may still be visible elsewhere.

The response also does not settle authorization. It does not, by itself, show whether a route-origin authorization covers each prefix, whether another registry records an address holder, or whether an announcement follows an intended routing policy. It reveals no traffic volume, customer path, upstream provider, facility, router or physical link. The correct claim is narrow: RIPEstat reported AS393598 as announced and returned three /24 prefixes at a defined time.

The organisation page confirms context, not topology

Affinity’s Who We Are page describes the organisation as a Saskatchewan-born co-operative financial institution owned by its members. It also says Affinity operates only in Saskatchewan. That first-party description helps connect the public brand to the Saskatchewan organisation named in ARIN’s entity record.

It should not be used to fill gaps in the network evidence. The page does not identify AS393598, the three observed prefixes, a hosting design, an upstream provider or a member-service path. A regional operating footprint does not mean that every supporting system, route or supplier is physically located in Saskatchewan. Likewise, a public ASN record does not establish that online banking, payments or any other product uses that routing domain.

This separation avoids two common errors. The first is to treat a company description as a topology map. The second is to treat public route data as a review of the company’s products. Neither move is supported here. The source set offers no basis for rating Affinity’s financial products, security controls, availability, regulatory compliance or operational resilience.

Three layers answer three different questions

The evidence becomes clearer when each source is allowed to do one job:

Evidence layer What it can answer What remains open
ARIN ASN and entity records Which organisation and coordination handles are recorded for AS393598 Current announcements, route authorization, reachability and service condition
RIPEstat overview and prefix data Which ASN and prefixes appeared in its time-stamped routing view Universal visibility, intended policy, traffic, topology and customer impact
Affinity’s organisation page How Affinity describes its ownership model and Saskatchewan scope Which network resources carry a specific service and how those services perform

The layers reinforce identity without becoming interchangeable. The ARIN and RIPEstat names align around Affinity Credit Union 2013, while the official site presents the shorter public brand Affinity Credit Union. That alignment supports a bounded network-identity Briefing. It does not convert a route observation into proof of legal ownership, or a registry record into proof of current operation.

Who can use the distinction

Network operators can start with AS393598 and the three observed prefixes when checking whether a route belongs in an investigation. They should then compare current BGP views, routing policy and authorization data rather than assuming the public snapshots answer every question.

Incident responders can use the registry handles to find a coordination boundary while keeping the suspected failure layer open. A user-facing problem might involve routing, domain-name resolution, an application, an identity provider, a payment dependency or a local access network. The presence of an ASN in public data does not identify which layer failed.

Vendors and service teams can ask whether a contracted product actually depends on AS393598, which other networks sit on its delivery path, and what dated test supports a continuity claim. Members and customers should not be expected to infer those details from registry or route data. A public routing identity is useful accountability infrastructure, but it is not a service-level report.

What stronger conclusions would require

A current routing assessment would need observations from defined times and vantage points. Route-origin validation could test whether an announcement is covered by the relevant authorization. Operator telemetry could show session state, interface condition and traffic. A traced application request could connect a user-visible service to a network path. A dated failover exercise could test a specific continuity claim.

Each item answers a separate question. None should be inferred from the five public sources used here, and the absence of that additional evidence is not evidence that Affinity’s network has failed. It simply marks where this Briefing must stop.

What to watch

  • a change to the AS393598 name, registrant handle or events in ARIN RDAP;
  • a change to the ACU-67 organisation record or coordination boundary;
  • a later RIPEstat view that adds, removes or changes the observed prefix timelines;
  • route-authorization evidence that establishes the intended origin for a listed prefix;
  • dated operational evidence connecting AS393598 to a specific service or continuity test.

Every future observation should retain its timestamp and evidence layer. Registry records, route observations and service tests can all be accurate while describing different parts of reality.

Sources

AS393598 provides a precise public identity for a routing domain recorded against Affinity Credit Union 2013. RIPEstat adds dated evidence that the ASN and three /24 prefixes appeared in its routing view. The value of those records lies in their precision and their boundaries: they help readers identify and investigate a network without turning a registry entry or route snapshot into an unsupported judgment about service, security or financial products.