Summary

  • ARIN's 4 November cumulative transfer original adds two RESOURCE_TRANSFER rows from Town of Georgina to The Regional Municipality of York, both timed 2026-11-03T21:50:57Z. Each repeats 199.201.121.0–199.201.123.255 as its 768-address original_set. The actual transfer_set fields are the two outer /24s, 199.201.121.0/24 and 199.201.123.0/24: 512 addresses together.
  • Current ARIN RDAP identifies the first /24 and the third with registrant RMY, while the middle /24 retains CTG-110. ARIN's RMY entity is The Regional Municipality of York; CTG-110 is the Town of Georgina. The three exact directory objects match the transfer-set geometry.

The transfer file offers a small arithmetic trap. It prints the same original_set199.201.121.0 through 199.201.123.255—in each of the two rows. That interval contains three /24s, or 768 IPv4 addresses. Add the two original fields as if each were a separate sale and the apparent volume becomes 1,536. Read ARIN's transfer_set instead and the movement is 256 plus 256: 512 addresses. The remaining 256 are not an omitted transaction. They are the exact middle /24, still registered to Georgina.

The two recorded transfers are unusually neat. Both are ARIN-to-ARIN, Canada-coded, and both carry RESOURCE_TRANSFER at 21:50:57 UTC on 3 November. One moves 199.201.121.0–199.201.121.255 to York. The other moves 199.201.123.0–199.201.123.255 to York. There is a complete /24 between them, not an address typo or a gap in the original interval. ARIN's transfer-log format describes cumulative snapshots and resource sets. It does not turn two resource rows into two disclosed legal agreements.

The directory supplies the missing middle. ARIN RDAP returns an exact .121/24 object named RMY and an exact .123/24 object with the same name. Their registrant handle resolves to The Regional Municipality of York. Query .122/24 and the answer is CTG-110, resolving to the Town of Georgina. Those three separate answers matter more than a quick lookup of a broader range: they preserve who the registry currently names for each address.

The clocks line up to the second without becoming a story about packet movement. RDAP records registration of the two York /24 objects at 16:50:56-05:00, or 21:50:56 UTC; it marks the Georgina middle object's last change at that same second. The last-change time for York's .123/24 is one second later, matching the transfer-log second. These are administrative timestamps in ARIN's public records. They place the three pieces in one coordinated filing window; they do not date a contract signing or a routing cutover.

There is a useful institutional tension in the shape. A regional municipality is now the named registrant at both ends of a three-part run, and a town remains the named registrant in the centre. A spreadsheet that aggregates all 768 addresses under the recipient would erase the town's surviving /24. A spreadsheet that sees the repeated original_set twice would triple the transferred volume. The exact RDAP objects make both errors visible without asking the reader to guess how the two governments arrange their services.

The public transfer rows and RDAP objects contain no municipal service agreement or dated routing record. Those documents would show why the two outer /24s moved and who operates the addresses; the registry evidence already settles the narrower question of current registration.

The 3 November cumulative original supplies the preceding snapshot for the two added rows. ARIN's transfer process guide explains the registry procedure; the exact transferred addresses come from the published rows and current RDAP, not from that general guide.