bgpreport

Network · data from 2026-11-12

AS270684 SOLUCOES SOUZA WEB LTDA

Registry name: AS270684 - SOLUCOES SOUZA WEB LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270684, 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.
200.187.104.0/24 Valid Other IRR onlyTC 666 99% 67
200.187.105.0/24 Valid Other IRR onlyTC 666 99% 67
200.187.106.0/24 Valid Other IRR onlyTC 666 99% 67
200.187.107.0/24 Valid Other IRR onlyTC 665 99% 67
2804:6fc8::/36 Valid Other IRR onlyTC 630 99% 69
2804:6fc8:e000::/36 Valid Other IRR onlyTC 629 99% 67
2804:6fc8:300::/40 Valid Other IRR onlyTC 104 16% 42
2804:6fc8:400::/40 Valid Other IRR onlyTC 104 16% 42
2804:6fc8:800::/40 Valid Other IRR onlyTC 104 16% 42

AS-SET

PeeringDB's irr_as_set for AS270684: TC::AS270684:AS-ALL. 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 (AS270684 isn't in the set, or no route object for AS270684 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 objectsAS270684 in itNot covered
TC::AS270684:AS-ALL TC 1213 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 13 are in fix.csv.

  • Route object: RIR9
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR200.187.104.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR200.187.105.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR200.187.106.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR200.187.107.0/24Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:6fc8::/36Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:6fc8:e000::/36Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6fc8:300::/40Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR2804:6fc8:400::/40Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR2804:6fc8:800::/40Route object only in TC. Add it in the RIR database for the space.104 of 636

Route objects not announced

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

200.187.104.0/22RADB, TCNo ROA
200.187.104.0/23TCNo ROA
200.187.106.0/23TCNo ROA
2804:6fc8::/32RADB, TCNo 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.