bgpreport

Network · data from 2026-11-12

AS63800 SERVER-G Group

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63800, 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.
2401:d20:10::/64 Invalid: maxLength Nonecovered by 2401:d20:10::/48 2 0%low visibility 1
2401:d20:1::/48 Valid Nonecovered by 2401:d20::/36 635 100% 70
2401:d20:f::/48 Valid Nonecovered by 2401:d20::/36 635 100% 70
2401:d20:66::/48 Valid Nonecovered by 2401:d20::/36 635 100% 70
2401:d20:99::/48 Valid Nonecovered by 2401:d20::/36 635 100% 70
103.131.151.0/28 Valid Nonecovered by 103.131.151.0/24 5 1%low visibility 5
103.131.151.0/24 Valid Other IRR onlyJPIRR 666 99% 69
2401:d20:10::/48 Valid Other IRR onlyJPIRR 636 100% 70
2401:d20:16::/48 Valid Other IRR onlyJPIRR 635 100% 70
2401:d20:19::/48 Valid Other IRR onlyJPIRR 635 100% 70
2401:d20:1c::/48 Valid Other IRR onlyJPIRR 635 100% 70
2401:d20:1d::/48 Valid Other IRR onlyJPIRR 635 100% 70
2401:d20:1e::/48 Valid Other IRR onlyJPIRR 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS63800: AS63800: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 (AS63800 isn't in the set, or no route object for AS63800 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 objectsAS63800 in itNot covered
AS63800:AS-SERVG JPIRRlists itself further down 6469 Yes 2

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

  • ROA: maxLength1
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength2401:d20:10::/64ROA 2401:d20::/36 AS63800 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2401:d20:10::/64.2 of 636
Route object: none2401:d20:10::/64No route object for it. A route object for 2401:d20:10::/48 with origin AS63800 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS63800 in the RIR database for the space.2 of 636
Route object: none2401:d20:1::/48No route object for it. A route object for 2401:d20::/36 with origin AS63800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63800 in the RIR database for the space.635 of 636
Route object: none2401:d20:f::/48No route object for it. A route object for 2401:d20::/36 with origin AS63800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63800 in the RIR database for the space.635 of 636
Route object: none2401:d20:66::/48No route object for it. A route object for 2401:d20::/36 with origin AS63800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63800 in the RIR database for the space.635 of 636
Route object: none2401:d20:99::/48No route object for it. A route object for 2401:d20::/36 with origin AS63800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63800 in the RIR database for the space.635 of 636
Route object: none103.131.151.0/28No route object for it. A route object for 103.131.151.0/24 with origin AS63800 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63800 in the RIR database for the space.5 of 673
Route object: RIR103.131.151.0/24Route object only in JPIRR. Add it in the RIR database for the space.666 of 673
Route object: RIR2401:d20:10::/48Route object only in JPIRR. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:d20:16::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:d20:19::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:d20:1c::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:d20:1d::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:d20:1e::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

44.30.62.0/24RADBNo ROA
103.131.150.0/23JPIRRNo ROA
2401:d20::/32JPIRRNo ROA
2401:d20::/36JPIRRValid
2401:d20:13::/48JPIRRValid
2401:d20:1a::/48JPIRRValid
2401:d20:1b::/48JPIRRValid
2401:d20:f000::/36JPIRRNo 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.