Autonomous system detail

AS967

Announced

AS967 announces 56 IPv4 and 12 IPv6 prefixes and peers with 2 other networks.

Summary

// analyst note
Routing observations are the combined snapshot from route-views2 and route-views6 at 2026-10-25T20:00:00.000Z. AS_PATH neighbours are not verified peers or commercial relationships.
IPv4 prefixes
56
~14.3K addresses
IPv6 prefixes
12
announced
Peer networks
2
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Low  ·  3 sources  ·  How this page is checked

AS967 is listed in IANA’s 1–1876 block as assigned by ARIN, and it had routes in the combined Route Views observation at 2026-10-25 20:00 UTC. The available evidence does not identify its operator, so the registration block does not establish who operates it or where it is based.

Across route-views2 and route-views6 together, the snapshot contained 57 IPv4 prefixes, 12 IPv6 prefixes, and an estimated 14,592 IPv4 addresses. The observed AS_PATH neighbours were AS932 and AS8796. These adjacencies show routing relationships in this snapshot; they do not establish commercial peering, transit, or customer relationships.

For identification, compare the prefixes and paths with a newer routing view and consult authoritative registration records for an explicit link between AS967 and an organization. Treat these figures as a dated view from the named collectors: routes absent from this snapshot cannot be taken as inactive, and routing counts alone say nothing about legitimacy or security.

Routing status
Routes were observed in the combined Route Views snapshot at 2026-10-25 20:00 UTC.
Identity
Operator and country are unknown from the supplied evidence.
Triage
Verify current announcements and seek an authoritative record explicitly linking AS967 to an operator before attributing activity.
IANA block
1–1876, assigned by ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Observation scope
combined RouteViews snapshot at 2026-10-25T20:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2
ASN
967 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Allocating RIR
ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
IPv4 prefixes
57 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2
IPv4 address estimate
14,592 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2
IPv6 prefixes
12 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2
Observed AS_PATH neighbours
AS932, AS8796 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2
[ 02 ] — Announced prefixes

What this network routes.

68 prefixes total · as observed by RouteViews at 2026-11-06 · one collector view, not a global census
// IPv4 prefixes56
  1. 103.132.164.0/24/24
  2. 103.132.165.0/24/24
  3. 103.132.166.0/24/24
  4. 103.132.167.0/24/24
  5. 103.247.28.0/24/24
  6. 103.247.29.0/24/24
  7. 167.88.176.0/24/24
  8. 167.88.177.0/24/24
  9. 167.88.180.0/24/24
  10. 186.241.104.0/24/24
  11. 186.241.105.0/24/24
  12. 186.241.106.0/24/24
  13. 186.241.107.0/24/24
  14. 206.237.11.0/24/24
  15. 206.237.14.0/24/24
  16. 209.146.112.0/24/24
  17. 209.146.113.0/24/24
  18. 209.146.114.0/24/24
  19. 209.146.115.0/24/24
  20. 23.236.66.0/24/24
  21. 23.236.67.0/24/24
  22. 23.236.68.0/24/24
  23. 23.236.69.0/24/24
  24. 38.147.160.0/24/24
  25. 38.147.161.0/24/24
  26. 38.207.160.0/24/24
  27. 38.207.161.0/24/24
  28. 38.207.164.0/24/24
  29. 38.207.165.0/24/24
  30. 38.207.172.0/24/24
  31. 38.207.173.0/24/24
  32. 38.207.174.0/24/24
  33. 38.207.175.0/24/24
  34. 38.207.180.0/24/24
  35. 38.207.181.0/24/24
  36. 38.207.184.0/24/24
  37. 38.207.185.0/24/24
  38. 38.55.100.0/24/24
  39. 38.55.101.0/24/24
  40. 38.55.102.0/24/24
  41. 38.55.103.0/24/24
  42. 38.55.104.0/24/24
  43. 38.55.105.0/24/24
  44. 38.55.106.0/24/24
  45. 38.55.107.0/24/24
  46. 38.95.76.0/24/24
  47. 38.95.77.0/24/24
  48. 45.221.112.0/24/24
  49. 45.221.113.0/24/24
  50. 45.221.114.0/24/24
  51. 45.221.115.0/24/24
  52. 91.213.174.0/24/24
  53. 91.213.186.0/24/24
  54. 91.213.189.0/24/24
  55. 91.216.190.0/24/24
  56. 91.217.160.0/24/24
// IPv6 prefixes12
  1. 2401:2660:2000::/36/36
  2. 2401:e9e0:1000::/36/36
  3. 2a06:5040:2000::/36/36
  4. 2602:f7c2:2000::/40/40
  5. 2401:1fe0:1::/48/48
  6. 2401:1fe0:2::/48/48
  7. 2401:1fe0:3::/48/48
  8. 2401:1fe0:4::/48/48
  9. 2401:1fe0:5::/48/48
  10. 2401:1fe0:6::/48/48
  11. 2401:1fe0::/48/48
  12. 2a0e:df80:a::/48/48
[ 03 ] — Notable peers & upstreams

Who it talks to.

2 observed neighbours
// Notable connections2 of 2 observed

Neighbours observed by RouteViews at 2026-11-06, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.

ASNOperatorRole
AS932 — —
AS8796 — —
Neighbours observed via public BGP collectors; not a complete peering list.