bgpreport

Network · data from 2026-11-12

AS58790 SERVER-G TestBed TeamFelNull

Registry name: TeamFelNull - SERVER-G Group, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58790, 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.

44.30.62.0/24 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
44.30.37.0/24 No ROA Other IRR onlyJPIRR, RADB 2 0%low visibility 2
2401:d20:1020::/48 Valid Nonecovered by 2401:d20:1020::/46 619 97% 67
2401:d20:1021::/48 Valid Nonecovered by 2401:d20:1020::/46 619 97% 67
2401:d20:1023::/48 Valid Nonecovered by 2401:d20:1020::/46 619 97% 67
2401:d20:1020::/46 Valid Other IRR onlyJPIRR 636 100% 69
2401:d20:1024::/46 Valid Other IRR onlyJPIRR 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS58790: AS58790:AS-SERVG. 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 (AS58790 isn't in the set, or no route object for AS58790 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 objectsAS58790 in itNot covered
AS58790:AS-SERVG JPIRRlists itself further down 6469 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 14 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none44.30.62.0/24No ROA covers it. Add a ROA for AS58790, maxLength 24.671 of 673
Route object: RIR44.30.62.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none44.30.37.0/24No ROA covers it. Add a ROA for AS58790, maxLength 24.2 of 673
Route object: RIR44.30.37.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.2 of 673
Route object: none2401:d20:1020::/48No route object for it. A route object for 2401:d20:1020::/46 with origin AS58790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58790 in the RIR database for the space.619 of 636
Route object: none2401:d20:1021::/48No route object for it. A route object for 2401:d20:1020::/46 with origin AS58790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58790 in the RIR database for the space.619 of 636
Route object: none2401:d20:1023::/48No route object for it. A route object for 2401:d20:1020::/46 with origin AS58790 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58790 in the RIR database for the space.619 of 636
Route object: RIR2401:d20:1020::/46Route object only in JPIRR. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:d20:1024::/46Route object only in JPIRR. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

2401:d20::/32JPIRRNo ROA
2401:d20:1020::/44JPIRRValid
2401:d20:1028::/46JPIRRValid
2401:d20:1060::/44JPIRRValid
2401:d20:1090::/44JPIRRValid

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.