bgpreport

Network · data from 2026-11-12

AS267492 ROBSON CARLOS THOMES

Registry name: AS267492 - ROBSON CARLOS THOMES - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267492, 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.
201.182.14.0/24 Valid Nonecovered by 201.182.14.0/23 670 100% 67
201.182.15.0/24 Valid Nonecovered by 201.182.14.0/23 670 100% 67
201.182.12.0/23 Valid Other IRR onlyRADB 672 100% 67
201.182.14.0/23 Valid Other IRR onlyRADB 672 100% 67
2804:4250::/32 Valid Other IRR onlyRADB 633 100% 68
2804:4250::/34 Valid Other IRR onlyRADB 633 100% 67
2804:4250:4000::/34 Valid Other IRR onlyRADB 633 100% 67
2804:4250:8000::/34 Valid Other IRR onlyRADB 633 100% 67
2804:4250:c000::/34 Valid Other IRR onlyRADB 633 100% 67
201.182.12.0/24 Valid Other IRR onlyRADB 322 48% 63
201.182.13.0/24 Valid Other IRR onlyRADB 322 48% 63

AS-SET

AS267492's PeeringDB record names no AS-SET.

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

  • Route object: none2
  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none201.182.14.0/24No route object for it. A route object for 201.182.14.0/23 with origin AS267492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267492 in the RIR database for the space.670 of 673
Route object: none201.182.15.0/24No route object for it. A route object for 201.182.14.0/23 with origin AS267492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267492 in the RIR database for the space.670 of 673
Route object: RIR201.182.12.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.182.14.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:4250::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4250::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4250:4000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4250:8000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4250:c000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR201.182.12.0/24Route object only in RADB. Add it in the RIR database for the space.322 of 673
Route object: RIR201.182.13.0/24Route object only in RADB. Add it in the RIR database for the space.322 of 673

Route objects not announced

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

186.233.96.0/22RADBNo ROA
201.182.12.0/22NTTCOM, RADBValid
2804:151c::/32RADBNo ROA
2804:4250::/33RADBValid
2804:4250:8000::/33RADBValid

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.