bgpreport

Network · data from 2026-11-12

AS393483 Yeo & Yeo CPAs & Business Consultants

Registry name: YEO-YEO - Yeo & Yeo CPAs & Business Consultants, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393483, 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.
70.34.166.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
47.45.8.0/24 Valid None 2 0%low visibility 2
23.153.220.0/24 Valid RIR databaseARIN 670 100% 68
2620:bb:5000::/48 Valid RIR databaseARIN 635 100% 70

AS-SET

AS393483'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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none70.34.166.0/24No ROA covers it. Add a ROA for AS393483, maxLength 24.2 of 673
Route object: RIR70.34.166.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none47.45.8.0/24No route object for it. Add a route object with origin AS393483 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS393483 is announced.

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.