bgpreport

Network · data from 2026-11-12

AS4557 SETG

Registry name: SOUTHEAST-TEXAS-GIGAPOP - Rice University, US · PeeringDB

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

Announced routes

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

2001:468:1af5::/48 No ROA Nonecovered by 2001:468:1a00::/40 634 100% 68
198.32.224.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
198.32.232.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
198.32.233.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
198.32.234.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
198.32.238.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
2001:468:1a00::/40 No ROA Other IRR onlyNTTCOM, RADB 635 100% 68
2001:468:1af4::/48 No ROA Other IRR onlyNTTCOM, RADB 635 100% 68
198.32.229.0/24 No ROA Other IRR onlyNTTCOM, RADB 20 3%low visibility 18
2001:468:1af1::/48 No ROA Other IRR onlyNTTCOM, RADB 17 3%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS4557: RADB::AS-SETG. 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 (AS4557 isn't in the set, or no route object for AS4557 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 objectsAS4557 in itNot covered
RADB::AS-SETG RADB 2332,097 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 35 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none2001:468:1af5::/48No ROA covers it. Add a ROA for AS4557, maxLength 48.634 of 636
Route object: none2001:468:1af5::/48No route object for it. A route object for 2001:468:1a00::/40 with origin AS4557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4557 in the RIR database for the space.634 of 636
ROA: none198.32.224.0/20No ROA covers it. Add a ROA for AS4557, maxLength 20.673 of 673
Route object: RIR198.32.224.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.32.232.0/24No ROA covers it. Add a ROA for AS4557, maxLength 24.671 of 673
Route object: RIR198.32.232.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.32.233.0/24No ROA covers it. Add a ROA for AS4557, maxLength 24.671 of 673
Route object: RIR198.32.233.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.32.234.0/24No ROA covers it. Add a ROA for AS4557, maxLength 24.671 of 673
Route object: RIR198.32.234.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.32.238.0/24No ROA covers it. Add a ROA for AS4557, maxLength 24.669 of 673
Route object: RIR198.32.238.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
ROA: none2001:468:1a00::/40No ROA covers it. Add a ROA for AS4557, maxLength 40.635 of 636
Route object: RIR2001:468:1a00::/40Route object only in NTTCOM, RADB. Add it in the RIR database for the space.635 of 636
ROA: none2001:468:1af4::/48No ROA covers it. Add a ROA for AS4557, maxLength 48.635 of 636
Route object: RIR2001:468:1af4::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.635 of 636
ROA: none198.32.229.0/24No ROA covers it. Add a ROA for AS4557, maxLength 24.20 of 673
Route object: RIR198.32.229.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.20 of 673
ROA: none2001:468:1af1::/48No ROA covers it. Add a ROA for AS4557, maxLength 48.17 of 636
Route object: RIR2001:468:1af1::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.17 of 636

Route objects not announced

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

192.58.120.0/24RADBNo ROA
198.32.224.0/24NTTCOM, RADBNo ROA
198.32.225.0/24NTTCOM, RADBNo ROA
198.32.226.0/24NTTCOM, RADBNo ROA
198.32.227.0/24NTTCOM, RADBNo ROA
198.32.228.0/24NTTCOM, RADBNo ROA
198.32.230.0/24NTTCOM, RADBNo ROA
198.32.231.0/24NTTCOM, RADBNo ROA
198.32.235.0/24NTTCOM, RADBNo ROA
198.32.236.0/24NTTCOM, RADBNo ROA
198.32.237.0/24NTTCOM, RADBNo ROA
198.32.239.0/24NTTCOM, RADBNo ROA
2001:468:1af0::/48NTTCOM, RADBNo ROA
2001:468:1af2::/48NTTCOM, RADBNo ROA
2001:468:1af3::/48NTTCOM, RADBNo 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.