bgpreport

Network · data from 2026-11-12

AS200454 Tomas Oliveira Valente Leite de Castro

Registry name: TOM-AS Tomas Oliveira Valente Leite de Castro, PT · PeeringDB

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

Announced routes

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

2602:faa5::/48 No ROA Nonecovered by 2602:faa5::/36 634 100% 67
199.16.240.0/22 No ROA Other origin only 2 0%low visibility 2
23.147.168.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
2a0a:6040:aa00::/40 Valid Other IRR onlyALTDB 634 100% 69
131.143.87.0/24 Valid RIR databaseARIN 667 99% 67
2a0f:b241:10::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS200454: RIPE::AS-LEGACY. 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 (AS200454 isn't in the set, or no route object for AS200454 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 objectsAS200454 in itNot covered
RIPE::AS-LEGACY RIPE 12184 Yes 1

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none2602:faa5::/48No ROA covers it. Add a ROA for AS200454, maxLength 48.634 of 636
Route object: none2602:faa5::/48No route object for it. A route object for 2602:faa5::/36 with origin AS200454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200454 in the RIR database for the space.634 of 636
ROA: none199.16.240.0/22No ROA covers it. Add a ROA for AS200454, maxLength 22.2 of 673
Route object: none199.16.240.0/22Route objects for it name AS397525. Add a route object with origin AS200454 in the RIR database for the space.2 of 673
ROA: none23.147.168.0/24No ROA covers it. Add a ROA for AS200454, maxLength 24.673 of 673
Route object: RIR2a0a:6040:aa00::/40Route object only in ALTDB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

64.93.80.0/22ALTDB, ARINNo ROA
199.16.241.0/24ALTDB, ARINNo ROA
199.16.242.0/23ARINNo ROA
199.16.242.0/24ALTDBNo ROA
199.16.243.0/24ALTDBNo ROA
208.85.8.0/22ALTDB, ARINNo ROA
208.85.8.0/23ARINNo ROA
208.85.8.0/24ARINNo ROA
2602:fa9b:c0::/48ARINValid
2602:faa5::/32ALTDBNo ROA
2602:faa5::/36ALTDBNo ROA
2602:faa5:53::/48ALTDBNo ROA
2602:faa5:fff::/48ALTDBNo 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.