bgpreport

Network · data from 2026-11-12

AS200790 ByteFizz

Registry name: BYTEFIZZ BYTEFIZZ LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200790, 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.
2a14:7583:e410::/46 Valid Other IRR onlyRADB 603 95% 68
2a0f:6284:8000::/48 Valid RIR databaseRIPE 635 100% 69
2a0f:6284:8001::/48 Valid RIR databaseRIPE 634 100% 69
2a0f:6284:8011::/48 Valid RIR databaseRIPE 634 100% 69
2a0f:6284:8013::/48 Valid RIR databaseRIPE 633 100% 69
2a0f:6284:8010::/48 Valid RIR databaseRIPE 631 99% 69
2a0f:6284:8012::/48 Valid RIR databaseRIPE 615 97% 68
2a0f:6284:8002::/48 Valid RIR databaseRIPE 611 96% 67
2a0f:6284:8015::/48 Valid RIR databaseRIPE 611 96% 67
2a0f:6284:8014::/48 Valid RIR databaseRIPE 607 95% 67
2a14:7583:e400::/40 Valid RIR databaseRIPE 604 95% 67
2a0f:6284:8000::/40 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS200790: RIPE::AS200790:AS-BYTEFIZZ. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS200790 isn't in the set, or no route object for AS200790 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS200790 in itNot covered
RIPE::AS200790:AS-BYTEFIZZ RIPE 1115 Yes 0

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 4 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR2a14:7583:e410::/46Route object only in RADB. Add it in the RIR database for the space.603 of 636

Route objects not announced

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

2a0f:6284:8016::/48RIPEValid
2a0f:6284:8017::/48RIPEValid
2a14:7583:e410::/44RIPEValid

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.