bgpreport

Network · data from 2026-11-12

AS398464 Buddy Software LLC

Registry name: BDDY - Buddy Software LLC, US · PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
26Route objects not announced registered with origin AS398464, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS398464, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
205.234.116.0/24 No ROA Other IRR onlyRADB 673 100% 67
77.247.116.0/22 Valid Other IRR onlyRADB 673 100% 67
185.217.166.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS398464's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 30 are in fix.csv.

  • ROA: none1
  • Route object: RIR3
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none205.234.116.0/24No ROA covers it. Add a ROA for AS398464, maxLength 24.673 of 673
Route object: RIR205.234.116.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR77.247.116.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR185.217.166.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS398464 whose prefix no peer sees AS398464 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.95.12.0/23RIPENo ROA
195.64.122.0/24RADBValid
2606:8940::/32RADBNo ROA
2a10:d500::/32RADBNo ROA
2a10:d501::/32RADB, RIPEValid
2a10:d502::/32RADBNo ROA
2a10:d503::/32RADBValid
2a10:d505::/32RADBValid
2a10:d506::/32RADBNo ROA
2a10:d507::/32RADBNo ROA
2a14:500::/29RADBNo ROA
2a14:700::/29RADBNo ROA
2a14:900::/29RADBNo ROA
2a14:b00::/29RADBNo ROA
2a14:f00::/29RADBNo ROA
2a14:1f00::/29RADBNo ROA
2a14:2100::/29RADBNo ROA
2a14:2500::/29RADBValid
2a14:2700::/29RADBValid
2a14:2b00::/29RADBValid
2a14:2d00::/29RADBValid
2a14:2f00::/29RADBValid
2a14:3300::/29RADBValid
2a14:3500::/29RADBValid
2a14:5a00::/29RADBNo ROA
2a14:6e00::/29RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.