bgpreport

Network · data from 2026-11-12

AS268037 FELIPE GERARDO ARAUJO DE LIMA

Registry name: AS268037 - OK NET INFOR LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268037, 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.
2804:56cc:c000::/40 No ROA Other origin only 1 0%low visibility 1
45.168.48.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.168.49.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.168.50.0/24 No ROA Other IRR onlyBBOI, RADB 671 100% 66
45.168.48.0/23 No ROA Other IRR onlyBBOI, RADB 669 99% 67
45.168.51.0/24 No ROA Other IRR onlyRADB 669 99% 67
2804:5700::/33 No ROA Other IRR onlyRADB 634 100% 67
2804:5700:6000::/35 No ROA Other IRR onlyRADB 634 100% 67
2804:5700::/35 No ROA Other IRR onlyRADB 632 99% 67
2804:5700:2000::/35 No ROA Other IRR onlyRADB 632 99% 67
2804:5700:4000::/35 No ROA Other IRR onlyRADB 632 99% 67
2804:5700:8000::/34 No ROA Other IRR onlyRADB 632 99% 67
45.168.48.0/22 No ROA Other IRR onlyBBOI, TC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS268037: TC::AS268037. 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 (AS268037 isn't in the set, or no route object for AS268037 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 objectsAS268037 in itNot covered
TC::AS268037 A single AS number, not a set: AS268037 (this network), 15 route objects.

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

  • ROA: none13
  • Route object: none1
  • Route object: RIR12
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:56cc:c000::/40No ROA covers it. Add a ROA for AS268037, maxLength 40.1 of 636
Route object: none2804:56cc:c000::/40Route objects for it name AS268024. Add a route object with origin AS268037 in the RIR database for the space.1 of 636
ROA: none45.168.48.0/24No ROA covers it. Add a ROA for AS268037, maxLength 24.671 of 673
Route object: RIR45.168.48.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.168.49.0/24No ROA covers it. Add a ROA for AS268037, maxLength 24.671 of 673
Route object: RIR45.168.49.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.168.50.0/24No ROA covers it. Add a ROA for AS268037, maxLength 24.671 of 673
Route object: RIR45.168.50.0/24Route object only in BBOI, RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.168.48.0/23No ROA covers it. Add a ROA for AS268037, maxLength 23.669 of 673
Route object: RIR45.168.48.0/23Route object only in BBOI, RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.168.51.0/24No ROA covers it. Add a ROA for AS268037, maxLength 24.669 of 673
Route object: RIR45.168.51.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:5700::/33No ROA covers it. Add a ROA for AS268037, maxLength 33.634 of 636
Route object: RIR2804:5700::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:5700:6000::/35No ROA covers it. Add a ROA for AS268037, maxLength 35.634 of 636
Route object: RIR2804:5700:6000::/35Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:5700::/35No ROA covers it. Add a ROA for AS268037, maxLength 35.632 of 636
Route object: RIR2804:5700::/35Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:5700:2000::/35No ROA covers it. Add a ROA for AS268037, maxLength 35.632 of 636
Route object: RIR2804:5700:2000::/35Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:5700:4000::/35No ROA covers it. Add a ROA for AS268037, maxLength 35.632 of 636
Route object: RIR2804:5700:4000::/35Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:5700:8000::/34No ROA covers it. Add a ROA for AS268037, maxLength 34.632 of 636
Route object: RIR2804:5700:8000::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none45.168.48.0/22No ROA covers it. Add a ROA for AS268037, maxLength 22.1 of 673
Route object: RIR45.168.48.0/22Route object only in BBOI, TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

45.168.50.0/23BBOI, RADBNo ROA
2804:5700::/32BBOI, RADB, TCNo ROA
2804:5700:c000::/34RADBNo 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.